Adjusting Logging Levels in Fusion

Fusion uses Apache Log4j 2 for logging and is configured using jetty/{connectors,api,ui}/resources/log4j2.xml . Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture.


During initialization, Log4J 2 will resolve this to a path based on the fusion components property [connectors, ui, api, and solr]. You can customize the -Dlog4j.configurationFile file, just edit one of Fusion components under bin folder.


For example; Edit connectors under bin folder

Log4j will first attempt to configure itself from configuration files. A configuration equivalent to the default would look like:

Log levels settings are as follows:


DEBUG designates fine-grained informational events that are most useful to debug a crawl configuration.

TRACE designates fine-grained informational events than DEBUG.

ERROR designates error events that might still allow the crawler to continue running.

FATAL designates very severe error events that will presumably lead the crawler to abort.

INFO designates informational messages that highlight the progress of the crawl at a coarse-grained level.

OFF has the highest possible rank and is intended to turn off logging.

WARN designates potentially harmful situations.


These levels allow you to monitor events of interest at the appropriate granularity without being overwhelmed by messages that are not relevant. When you are initially setting up your crawl configuration, you might want to use the DEBUG level to get all messages, and change to a less verbose level in production.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk