Fusion services come pre-configured to write log messages to stdout (common pattern in K8s) and send log messages to Logstash (deployed in our Helm chart). Logstash is configured to index log messages into the Fusion
The Log Viewer integrated into the Fusion Admin UI provides basic log analytics for the logs collected in
system_logs. You can also use your preferred log analytics stack, such as ELK, Splunk, DataDog, or similar.
For integration with an existing log infrastructure, you have two basic choices:
Disable Logstash and scrape logs from stdout
In your custom values YAML files, set
logstashEnabled: falsefor all services.
Configure your logging infrastructure to scrape logs from the stdout from each pod.
This is a very common pattern in Kubernetes and most modern log analytics solutions have good integration with Kubernetes.
Use Logstash to send logs
This is a good option if you use ELK but don’t have an existing integration with Kubernetes. This option requires some changes to the Logstash configuration in your custom values YAML file.
Elasticsearch is a common tool used to store and query logs and can be easily configured as an output for Logstash. Just include the
elasticsearchHost to our Helm chart and set it to
host:port. In most cases, the port number will be 9200, as in the example below.
logstash: elasticsearchHost: <elasticsearch-host>:9200