.NET agent release notesRSS

Fixes

• Attribute collections in the agent will now more reliably track the number of attributes contained, and allow updates to attributes that already exist in the collection when collection limits have been reached (255 global attributes, 65 custom attributes). (#1335)
• The agent has been updated to use System.Net.Http.HTTPClient to send data to New Relic instead of System.Net.WebRequest, in order to fix issue #897, as well as remove use of a deprecated library. (#1325)

Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/ or on NuGet.org.

Checksums

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

• Support for .NET 7 has been verified with the GA version of the .NET 7 SDK. Please note that if you use dynamically-created assemblies, there is a bug in .NET 7 that prevents them from being instrumented at this time.
• Application log fowarding can now be configured to capture and forward context data to New Relic. Details (including how to enable and configure this new feature) can be found here.
• The NewRelic.Agent NuGet package now includes the Linux Arm64 profiler. This can be found in the newrelic/linux-arm64 directory. Configure your CORECLR_PROFILER_PATH environment variable to use this version of the profiler when deploying to linux ARM64 targets.
• When finest logs are enabled, the transaction guid will be applied to attribute limit log messages, if present.

Fixes

• Resolves potential crash when using Infinite Tracing. #1319

Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/ or on NuGet.org.

Checksums

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

• Custom event limit increase
  • This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for max_samples_stored. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post. #1284

Checksums

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

• Add new environment variables to control SendDataOnExit functionality: NEW_RELIC_SEND_DATA_ON_EXIT, NEW_RELIC_SEND_DATA_ON_EXIT_THRESHOLD_MS. #1250
• Enables integration with CodeStream code-level metrics by default. This allows you to see golden signals in your IDE through New Relic CodeStream without altering agent configuration. Learn more here. For any issues or direct feedback, please reach out to support@codestream.com. #1255

Fixes

• Resolves an issue where the .NET Core agent could crash during application shutdown when SendDataOnExit functionality was triggered. #1254
• Resolves an issue where the .NET agent incorrectly injects the browser agent script inside HTML pages. #1247
• Resolves an issue where some instrumentation was missing for Microsoft.Data.SqlClient in .NET Framework. #1248
• Resolves an issue with local log decoration for NLog where the original log message was not included in the output. #1249
• Resolves an issue where the .NET agent failed to serialize custom attributes containing some non-primitive types. #1256
• Includes missing profiler environment variables in debug logs during application startup. #1255
• Resolves an issue where the .NET agent still sends up disabled event types during reconnecting period. #1251

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.20.262.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.

New Features

• Support of setting up labels via appsettings.json and app/web.config file. #1204
• Additional DEBUG-level logging of all environment variables.
• Forwarded application logs now capture exception details including, error message, error stack, and error class. #1228
  • Log events with no message will now be accepted if an exception is present in the log event.
  • The error stack is created using the stack of the inner exception, up to 5 levels deep, just like existing Agent error reporting.
• Adds a new SetName() method to the Agent API for spans which allows customization of segment/span/metric names. #1238

Fixes

• Resolves an issue where log forwarding could drop logs in async scenarios. #1174
• Resolves an issue where more logs were forwarded than expected from Microsoft.Extensions.Logging. #1237
• Resolves an agent configuration bug where values set in the MAX_EVENT_SAMPLES_STORED and MAX_TRANSACTION_SAMPLES_STORED environment variables, which configure the maximum samples stored per one-minute harvest interval, were not being properly converted to apply to the five-second harvest interval for those data types. #1239

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.19.353.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.

New Features

• Adds support for forwarding application logs to New Relic for .NET Framework 4.6.2 and newer applications using Microsoft.Extensions.Logging. #1172
• Additional agent configuration options are now visible and easily accessible through the UI on NR1. Agent configuration is also now reported during agent connect. This information can be seen in the APM->Environment->Agent Initialization view. #1174

Fixes

• Resolves an issue with transaction trace aggregation where the slowest transaction trace was not always captured due to a race condition. #1166
• Adds an ignore rule to prevent profiling SMSvcHost.exe. #1182
• Updates applicationLogging attribute log.level to be level. #1144

Deprecations/Removed Features

• This is a major release of the agent, and contains breaking changes. See the migration guide for details.
• This agent release targets .NET Framework 4.6.2 and .NET Standard 2.0. The minimum supported runtime versions for profiled applications are .NET Framework 4.6.2+ and .NET Core 3.1+.
• The scriptable installers have been removed. #1170
• Windows installation files have been consolidated and renamed. #1187
• The Linux installation packages have been renamed. #1180
• Castle.Monorail instrumentation has been removed. #1177

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.

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.