- logback 1.1.x must be configured and working in the application.
- The New Relic Java agent must be enabled using the
-javaagentcommand-line parameter. - You must be using at least version 5.6.0 of the Java Agent.
There are some changes to your application to use the New Relic Logback Extension. All steps are required.
Optional: Configuration Options for setting max stack size or collecting MDC.
Refer to Maven Central for the appropriate snippets.
Update your logging configuration xml to include the <encoder> element like below.
<appender name="LOG_FILE" class="ch.qos.logback.core.FileAppender">
<file>logs/app-log-file.log</file>
<encoder class="com.newrelic.logging.logback11.NewRelicEncoder"/>
</appender>Why? The New Relic log format is a tailored JSON format with specific fields in specific places that our log forwarder plugins and back end rely on. At this time, we don't support any customization of that format.
Update your logging configuration xml to add this section. Change "LOG_FILE" to the name of the appender
you updated in the previous step.
<appender name="ASYNC" class="com.newrelic.logging.logback11.NewRelicAsyncAppender">
<appender-ref ref="LOG_FILE" />
</appender>Why? The New Relic log format includes New Relic-specific data that must be captured on the thread the log message
is coming from. This appender captures that information before passing to the standard AsyncAppender logic.
Update your logging configuration xml to connect the root (and other) loggers to the ASYNC appender you configured
in the previous step.
<root level="INFO">
<appender-ref ref="ASYNC" />
</root>