.NET agent release notesRSS

Notice: If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer. We encourage you to adopt the newer version due to bug #1230, which we fixed in #1237, that was resolved in .NET agent version 10.1.0.

New Features

• Adds support for logging metrics, forwarding application logs, and enriching application logs written to disk or standard out for NLog versions v5 and v4. #1087
• Adds integration with CodeStream, introducing code-level metrics! Golden signals visible in your IDE through New Relic CodeStream. Learn more here. For any issues or direct feedback, please reach out to support@codestream.com
• Updates the following installation methods to check for and remove deprecated files. (#1104)
  • MSI Installer
  • Azure Site Extension
  • RPM package
  • DEB package

Fixes

• Upgrades Newtonsoft.Json to version 13.0.1 to address potential security vulnerabilities identified by Snyk (#1107)
• The agent will now send the values of application logging config options (e.g. application_logging.forwarding.enabled) to the agent initialization settings page. (#1135)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.29.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Notice: If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer. We encourage you to adopt the newer version due to bug #1230, which we fixed in #1237, that was resolved in .NET agent version 10.1.0.

Fixes

• Fixes an issue with log forwarding where an agent could momentarily forward logs even if the feature had been disabled at an account level. (#1051)
• Adds an internal list of deprecated instrumentation xml files which will cause the profiler to ignore deprecated instrumentation. This feature avoids an issue where orphaned deprecated log forwarding instrumentation could conflict with newer instrumentation. (#1051)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.28.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Notice: If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer. We encourage you to adopt the newer version due to bug #1230, which we fixed in #1237, that was resolved in .NET agent version 10.1.0.

APM logs in context

Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature, see the APM logs in context documentation. For additional configuration options, see the .NET logs in context documentation. To learn about how to toggle log ingestion on or off by account, see our documentation to disable automatic logging via the UI or API.

New features

• Error messages in error traces and error events now retain up to 1023 characters instead of 255 characters. #1058
• New environment variables have been added for AllowAllHeaders and Attributes configuration settings. See our configuration documentation for more details. #1059
• Introduces environment variables to enable/disable cloud detection to facilitate customer use cases and reduce errors in logs. (#1061)
• New environment variables have been added for all Proxy configuration settings. See our configuration documentation for more details. #1063
• Introduces a new configuration option to force custom instrumentation to create new transactions in async scenarios versus re-using an existing transaction. #1071

Fixes

• Fixes Agent fails to execute explain plan for parameterized stored procedure. (#1066)
• Fixes getting duplicate logs using log forwarding and Serilog. #1076

Deprecations

Microsoft has officially EOLed:

• .NET Framework versions 4.5.1, 4.5.2, and 4.6.1 on Apr 26, 2022.
• .NET Core version 2.0 on October 1, 2018.
• .NET Core version 2.1 on August 21, 2021.
• .NET Core version 2.2 on December 23, 2019.
• .NET Core version 3.0 on March 3, 2020.

The official product lifecycle start and end dates can be found on the Microsoft documentation for .NET Framework and for .NET Core onward. Our .NET agent support of these framework versions will continue as is with the released versions. In a future major release, we will target .NET Framework 4.6.2 and .NET Core 3.1 onwards.

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.28.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Notice: If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer. We encourage you to adopt the newer version due to bug #1230, which we fixed in #1237, that was resolved in .NET agent version 10.1.0.

Fixes

• Adds missing instrumentation for application logging feature when using the MSI installer (#1055)
• Fixes issue on Linux when specifying a non-default profiler log directory with non-existent intermediate directories. (#1051)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Notice: For the new application logging features, if you install using the MSI, please update to version 9.7.1 or later.

Notice: If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer. We encourage you to adopt the newer version due to bug #1230, which we fixed in #1237, that was resolved in .NET agent version 10.1.0.

New Features

• Adds support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary view for Log4net, Serilog, and Microsoft.Extensions.Logging. This is enabled by default in this release. (#1034)
• Adds support for forwarding application logs to New Relic. This automatically sends enriched application logs for Log4net, Serilog, and Microsoft.Extensions.Logging. This is disabled by default in this release. (#1034)
• Adds support for enriching application logs written to disk or standard out for Log4net, Serilog, Microsoft.Extensions.Logging. This can be used with another log forwarder if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release. To learn more about APM logs in context and the configuration options, please see the documentation here. (#1034)
• Adds flexibility to what is accepted to enable/disable boolean environment variables per FR #1008. "0"/"1", and case insensitive "true"/"false" are now accepted. (#1033)

Fixes

• Adds a new environment variable NEW_RELIC_DISABLE_APPDOMAIN_CACHING for customers to try when experiencing #533 high lock contention related to AppDomain.GetData() usage by the agent when profiling .NET Framework applications. (#1033)

Deprecations

• The scriptable installers are now deprecated and will be removed from the download site in a future major release. (Issue: #571)
• The established release installers are now deprecated and will be removed from the download site in a future major release. (Issue: #578)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Fixes

• Fixes application pool allow/deny listing bug introduced in 9.5.0 (#1015)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Features

• Adds new supportability metrics to track agent endpoint data usage. New metrics will be reported under the Supportability/DotNET/Collector namespace. (#899)
• Uses IMDSv2 instead of IMDSv1 to gather utilization details for AWS hosted instances. 965

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Fixes

• Fixes application crashes on Alpine Linux introduced in 9.5.0. (#929)

Checksums

Support statement

New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0.

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Features

• Internal improvements to runtime detection logic in the profiler component of the agent. (#891)

Fixes

• Fixed an issue with NuGet package metadata. (#901)

Checksums

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0.

Upgrading

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.