With our .NET APM agent, you can get logs in context, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see APM logs in context.
You have three options to configure APM logs in context to send your app's logs and linking metadata automatically to New Relic. Supported frameworks for automatic logs in context using in agent forwarding include:
- log4net: 1.2.10+ (.NET Framework), 2.0.10+ (.NET Core). Requires .NET Agent v9.7.0+.
- Note: Many versions of Sitecore use log4net for logging. However, this version of log4net is currently unsupported by the agent.
- NLog: 4.1+ (.NET Framework), 4.5+ (.NET Core). Requires .NET Agent v9.7.0+.
- Serilog: 2.0+ (.NET Framework), 2.5+ (.NET Core). Requires .NET Agent v9.7.0+.
- Microsoft.Extensions.Logging: 3.0+. Requires .NET Agent v9.7.0+ (.NET Core), Agent v10.0.0+ (.NET Framework).
While you wait for your data to come in...
Did this doc help you install?
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.
To make the most of your logging data:
- On the APM Summary page, click your Web transaction time chart to view logs associated with a specific point in time.
- Check your app's Errors inbox to view the logs associated with your errors.
- Use distributed tracing to see the logs associated with individual traces.
- Explore more logging data across your platform with our Logs UI.
- Set up alerts based on log output and severity.
- Query your data using our specialized UI for logs data, and create dashboards with the results.
Typically your logs will start to appear less than a minute after you enable APM logs in context. Check your app's Triage > Logs section. You will also start seeing log patterns related to the error there.
If you don't see any logs for errors or traces, there may not be any for your app. Try refreshing the UI page, or change the selected time period.
APM logs in context automatically forwards APM agent log data and is enabled by default. This can have a negative impact on your security, compliance, billing, or system performance. For more information, or if you need to adjust the default setting, follow the procedures to disable automatic logging.
If you need to use the manual process to set up logs in context for .NET, follow these steps:
- Make sure you have already set up logging in New Relic. This includes configuring a supported log forwarder that collects your application logs and extends the metadata that is forwarded to New Relic.
- Install or update to the latest .NET agent version, and enable distributed tracing. Use .NET agent version 8.21 or higher and the New Relic .NET agent API version 8.21 or higher for logs in context.
- Install or update to Microsoft .NET Framework 4.5 or higher or .NET Core 2.0 or higher.
- Install and configure any of the following logging extensions to enrich your log data, including:
- Check your log data in the New Relic UI.
You can use the Apache log4net version 2.0.8 or higher extension to link your log data with related data across the rest of the New Relic platform.
You can use our NLog 4.5 or higher extension to link to your log data with related data across the rest of the New Relic platform.
You can use our Serilog extension to link to your log data with related data across the rest of the New Relic platform. This requires: