Fusion services come pre-configured to write log messages to stdout (common pattern in K8s) and index log messages into the Fusion
system_logs collection via a pulsar message queue processed by the
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 Log forwarding and scrape logs from stdout
In your custom values YAML files, set
global: logging: disablePulsar: true
Configure your logging infrastructure to scrape logs from the stdout from each pod.
It is possible to setup fusion to output json formatted logs to stdout to ease configuration of log forwarders, to enable this add the following to the values file:
global: logging: jsonOutput: true
+ 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. Fusion can be configured to send logs directly to a user’s already configured logstash instance by setting the following in your values file:
global: logging: logstashHost: <logstash_host>