Configure Fusion Logging in Fusion 4.1 and 4.2

Fusion uses the Apache Log4j 2 logging framework with Jetty to log each of the Fusion components.

Logging is configured with an XML configuration file named log4j2.xml. Log levels, frequencies, and log rotation policy can be configured by changing these configuration files:

API service

VAR-FUSIONPATH/conf/api-log4j2.xml

Connectors

VAR-FUSIONPATH/conf/connectors-classic-log4j2.xml

VAR-FUSIONPATH/conf/connectors-rpc-log4j2.xml

Solr

VAR-FUSIONPATH/conf/solr-log4j2.xml

Spark

VAR-FUSIONPATH/conf/spark-driver-launcher-log4j2.xml

VAR-FUSIONPATH/conf/spark-driver-log4j2.xml

VAR-FUSIONPATH/conf/spark-driver-scripted-log4j2.xml

VAR-FUSIONPATH/conf/spark-executor-log4j2.xml

VAR-FUSIONPATH/conf/spark-master-log4j2.xml

VAR-FUSIONPATH/conf/spark-worker-log4j2.xml

SQL

VAR-FUSIONPATH/conf/sql-log4j2.xml

ZooKeeper

VAR-FUSIONPATH/conf/zookeeper-log4j2.xml

Other Fusion services

VAR-FUSIONPATH/conf/proxy-log4j2.xml

The Log4j2 Configuration guide provides documentation and examples of all logging configuration options.

The Fusion log shipper parses Fusion Java, HTTP, and garbage collector logs and sends them to a system collection. This system collection is used for dashboards in the Fusion UI.

Log shipping is enabled by default. You can disable log shipping, adjust which logs are parsed, or send log files to an external Solr instance or cluster, or to a custom collection name. For the configuration and details, see VAR-FUSIONPATH/conf/fusion.cors (fusion.properties in Fusion 4.x) (on Unix or macOS) or fusion\latest.x\conf\fusion.cors (fusion.properties in Fusion 4.x) (on Windows).