Integrate Fusion with Your Logging Infrastructure

Table of Contents

Disable Log forwarding and scrape logs from stdout
Use Logstash to send logs

Fusion services come pre-configured to write log messages to stdout and index log messages into the Fusion system_logs collection using a Pulsar message queue processed by the fusion-log-forwarder component.

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 Elastic Stack, Splunk, or DataDog.

For integration with an existing log infrastructure, you have two basic choices:

Disable log forwarding and scrape logs from stdout
Use Logstash to send logs

Disable Log forwarding and scrape logs from stdout

In your custom values YAML files, set the global logging disablePulsar value to true:
```
global:
  logging:
    disablePulsar: true
```
Configure your logging infrastructure to scrape logs from the stdout from each pod.

It’s possible to set up Fusion to output JSON logs to stdout to ease configuration of log forwarders. This is a common pattern in Kubernetes, and most modern log analytics solutions have good integration with Kubernetes.

To do this, set the global logging jsonOutput value to true:

global:
  logging:
    jsonOutput: true

Use Logstash to send logs

Fusion can be configured to send logs directly to a user’s pre-configured logstash instance. This is a good option if you use ELK, but you don’t have an existing integration with Kubernetes.

To do this, set the global logging logstashHost value to match your logstash_host value:

global:
  logging:
    logstashHost: <logstash_host>