APM logs in context connects your logs with all of your telemetry data for your apps, hosts, and other entities. Bringing all of this data together in a single tool helps you quickly:
- Cut through the noise of thousands of logs when troubleshooting time-critical issues, so you automatically see only the most relevant logs.
- Navigate within multiple types of telemetry data, and have the data correlate back to the original issue.
- Easily drill down into more detailed information from the same place in the UI.
- Find the log lines that you need to identify and resolve a problem.
For more information, including examples, learn how to get started with APM logs in context.
In the Go agent, there are currently two options to configure APM logs in context to send your app's logs and linking metadata automatically to New Relic. For more information about the application logging settings in the following procedure, see our documentation about Go agent configuration.
Your logs may include sensitive information protected by HIPAA or other compliance protocols. By default we obfuscate number patterns that appear to be for items such as credit cards or Social Security numbers, but you may need to hash or mask additional information.
For more information, see our documentation about obfuscation expressions and rules. You can hash or mask your log data by using the New Relic UI or by using NerdGraph, our GraphQL API.
After you set up APM logs in context, make the most of your logging data:
- Explore the logging data across your platform with our Logs UI.
- See your logs in context of your app's performance in the APM UI. Troubleshoot errors with distributed tracing, stack traces, application logs, and more.
- Get deeper visibility into both your application and your platform performance data by forwarding your logs with our infrastructure monitoring agent. Review your infrastructure logs in the UI.
- Set up alerts.
- Query your data and create dashboards.