Combined with New Relic Logs, logs in context for the Java agent connects your Logs and APM data in New Relic, giving full context to high-level events and providing high value data to specific log lines. This document explains how to configure logs in context and start getting log data.
Compatibility and requirements
Access to logs in context requires a New Relic APM Pro or Pro trial subscription and enabling of distributed tracing. Before enabling distributed tracing, read the transition guide to learn about the effects on existing APM features and set-up recommendations.
To use New Relic Logs with the Java agent, ensure your configuration meets the following requirements:
- New Relic Logs enabled, with a compatible log forwarding plugin installed
- Java agent 5.6.0 or higher: Install or update
Configure logs in context for Java
Choose an extension to see specific instructions:
- Dropwizard v1.3 extension
- java.util.logging extension
- Logback extension
- Log4j 1.x extension
- Log4j 2.x extension
Use Spring or Spring Boot and not sure which extension you need? See our Spring documentation.
Now that you've set-up APM logs in context, here are some potential next steps:
- Explore your data using the Logs UI.
- Troubleshoot errors with distributed tracing, stack traces, application logs, and more.
- Query your data and create custom dashboards, charts, or alerts.