.NET agent release notesRSS

New Features

• Updated support for RabbitMQ
  • Adds support for .NET Core applications using RabbitMQ.Client.
  • Adds support for RabbitMQ.Client version 6.2.1.
  • Not supported: Distributed Tracing is not supported with the RabbitMQ AMQP 1.0 plugin.
• Adds configuration Environment Variables
  • Adds MAX_TRANSACTION_SAMPLES_STORE - the maximum number of samples stored for Transaction Events.
  • Adds MAX_EVENT_SAMPLES_STORED - the maximum number of samples stored for Custom Events.
  • Adds NEW_RELIC_LOG - the unqualifed name for the Agent's log file.

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

Download URLs

Download the appropriate release for your New Relic .NET agent:

https://download.newrelic.com/dot_net_agent/latest_release

Fixes

• Fixes Issue #224 where leading "SET" commands will be ignored when parsing compound SQL statements. (#370)
• Fixes Issue #226 where the profiler ignores drive letter in HOME_EXPANDED when detecting running in Azure Web Apps. (#373)
• Fixes Issue #93: when the parent methods are blocked by their asynchronous child methods, the agent deducts the child methods' duration from the parent methods' exclusive duration.(#374)
• Fixes Issue #9 where the agent failed to read settings from appsettings.{environment}.json files. (#372)
• Fixes Issue #116 where the agent failed to read settings from appsettings.json in certain hosting scenarios. (#375)
• Fixes Issue #234 by reducing the likelihood of a Fatal CLR Error. (#376)
• Fixes Issue #377 when using the AddCustomAttribute API with Microsoft.Extensions.Primitives.StringValues type causes unsupported type exception. (378)

Checksums

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.

New Features

• .NET 5 GA Support
  We have validated that this version of the agent is compatible with .NET 5 GA. See the compatibility and requirements for .NET Core page for more details.

Fixes

• Fixes Issue #337 by removing obsolete code which was causing memory growth associated with a large number of transaction names.
• PR #348: guards against potential exceptions being thrown from the agent API when the agent is not attached.

Checksums

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.

New Features

• .NET 5 RC2 Support
  We have validated that this version of the agent is compatible with .NET 5 Release Candidate 2.

Fixes

• Fixes #301 where the agent incorrectly parses server-side configuration causing agent to shutdown.#310
• Modifies WCF Instrumentation to address #314 by minimizing the reliance upon handled exceptions during the attempt to capture CAT and DT payloads.

Checksums

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.

Fixes

• Fixes #223 so the agent can be compatible with ASP.NET Core 5 RC1.
• Fixes issue in .NET 5 applications where external calls made with HttpClient may not get instrumented. For example, calls made with HttpClient.GetStringAsync would be missed. (#235)
• Fixes issue #257 where .NET Standard Libraries that do not reference mscorlib fail to be instrumented in .NET Framework applications.
• Reduces the performance impact of large amounts of instrumentation. See issue #269 for more information.

Checksums

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.

New Features

• Proxy Password Obfuscation Support
  Agent configuration supports the obfuscation of the proxy password. The New Relic Command Line Interface (CLI) may be used to obscure the proxy password. The following documentation describes how to use an obscured proxy password in the .NET Agent configuration.
• MySqlConnector Support
  The MySqlConnector ADO.NET driver is instrumented by default. Fixes #85 and implements this suggestion.
• Nullable Reference Type support in the API
  Enables nullable reference types that are part of the C# 8.0 language specification and updates the signatures of API methods accordingly. There should be no required changes in API usage.
• Improved Support for NetTCP Binding in WCF Instrumentation
  When the NetTCP Binding type is used in Windows Communication Foundation (WCF), the Agent will now send and receive trace context information in support of Distributed Tracing (DT) or Cross Application Tracing (CAT). Implements #209.

Fixes

• Fixes an issue that may cause InvalidCastException due to an assembly version mismatch in Mvc3 instrumentation.
• Fixes an async timing issue that can cause the end time of Task-returning methods to be determined incorrectly.

Checksums

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.

Notes

The 6.x agent supports legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 or higher, or if you are on .NET Core, use the 8.x agent versions.

Download URLs

Download the appropriate release for your New Relic .NET agent:

• .NET Framework

New Features

• The .NET Agent is now open source!
  The New Relic .NET agent is now open source! Now you can view the source code to help with troubleshooting, observe the project roadmap, and file issues directly in this repository. We are now using the Apache 2 license. See our Contributing guide and Code of Conduct for details on contributing!
• SSL Required
  In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer supported. All communication with New Relic services will occur via SSL.
• EU Data Center Support
  Adds support for communicating with New Relic's EU Data Center. Please review our docs site for further information.

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.

New Features

• Expected Errors Support
  Certain errors that are expected within the application may be identified so that they will not be counted towards the application's error rate and Apdex Score. Only errors that truly affect the health of the application will be alerted on. Please review the following documentation for details on how to configure Expected Errors.

• Ignored Errors Enhancements
  Certain errors may be identified in configuration so that they will be ignored. These errors will not be counted towards the application's error rate, Apdex score, and will not be reported by the agent. Please review the following documentation for details on how to configure Ignored Errors.

  • New configuration element <ignoreMessages>supports filtering based on the error message.
  • Please note that the <ignoreErrors> configuration element has been deprecated and replaced by <ignoreClasses>. The .NET Agent continues to support this configuration element, but its support may be removed in the future.

Fixes

• Garbage Collection Performance Metrics for Windows
  Fixes an issue where Garbage Collection Performance Metrics may not be reported for Windows Applications.
• Maintaining newrelic.config on Linux package upgrades
  Fixes an issue where newrelic.config was being overwritten when upgrading the agent via either rpm/yum (RedHat/Centos) or dpkg/apt (Debian/Ubuntu).

Checksums

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.

New Features

• The .NET agent is now open source!
  The New Relic .NET agent is now open source! Now you can view the source code to help with troubleshooting, observe the project roadmap, and file issues directly in this repository. We are now using the Apache 2 license. See our Contributing guide and Code of Conduct for details on contributing!

Fixes

• Memory usage reporting for Linux
  Fixes issue where applications running on Linux were either reporting no physical memory usage or using VmData to report the physical memory usage of the application. The agent now uses VmRSS through a call to Process.WorkingSet64 to report physical memory usage. See the dotnet runtime discussion and the proc man pages for more details about this change.
• Infinite Tracing performance
  Fixes issue where the agent may consume too much memory when using Infinite Tracing.
• .NET 5 support
  Fixes issue with applications running on .NET 5 that prevented instrumentation changes at runtime (either though editing instrumentation XML files or through the Live Instrumentation editor Beta).

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.