.NET agent release notesRSS

Download URLs

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

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

New Features

• Adds automatic capture of datastore information for MongoDB driver versions 2.6.x, 2.5.x, 2.4.x, and 2.3.x.
• [.NET Core 2.0] Adds thread profiler support for .NET Core applications running on Windows.

Fixes

• Improved the agent's ability to recover from certain connection related issues without requiring an agent or application restart.

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/previous_releases

New Features

• Replaces the request_uri attribute with request.uri. Adds the request.uri attribute to transaction traces and error traces. If you wish to control the presence of this attribute please follow the instructions at https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-...

Fixes

• [.NET Framework] Fixes issue of recursive directory creation when recovering from a failed upgrade install in the scriptable installer.
• [.NET Framework] Fixes issue where Thread Profiler fails to resolve types and method names. These would appear as UnknownClass.UnknownMethod(<#>) in a profile.

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 Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

• Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
• Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
• [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.
• [.NET Framework] Fixed issue introduced in agent version 8.1.709.0 that caused some .NET Framework applications to throw the following exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.

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 Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

• Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
• Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
• [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.

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

• Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries which have multiple statements.

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

• Adds stripExceptionMessages configuration option to the newrelic.config file. When enabled, this will remove error messages from errors that are reported to New Relic. This is the same behavior as having High-security mode enabled but can be used without High-security mode. The default value for this setting is false.

Fixes

• Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries that have multiple statements.

Other Changes

• In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer allowed.
• WCF service parameters are now captured as request.parameters.* attributes and are no longer sent as service.request.* attributes.
• Minimum version required for use in EU Datacenter.

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

• Improved metadata collection for cloud providers. The agent now collects additional metadata when running in AWS, GCP, and Azure. This information is used to provide an enhanced experience when the agent is deployed on those platforms.

Fixes

• Fixed an issue where transactions could be dropped when they included datastore segments and the following exception was logged: NewRelic ERROR: An exception occurred while doing some background work: System.NullReferenceException: Object reference not set to an instance of an object.
• Fixed an issue where SOAP instrumentation would report System.Reflection.TargetInvocationException errors when a more specific error existed. Inner exceptions will now be reported when they exist.

Deprecation Warnings

The follow items are considered deprecated and will be removed with the upcoming 8.x major release:

• Disabling agent HTTPS communication via the service SSL configuration will no longer be allowed starting in 8.x versions of the agent.
• WCF service parameters will no longer be sent as service.request.* attributes starting in 8.x versions of the agent. These parameters will be sent in the form request.parameters.*.

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

• Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled.

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

• Modifying custom instrumentation XML files can now be performed without having to restart the monitored application. Instrumentation updates will be applied ‘dynamically’ at runtime. This feature required functionality provided by new APIs introduced in .NET Framework 4.5 and newer, which this release also addresses (see ‘Framework Support’ section below).

Fixes

• Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled.
• Fixed an issue with automatic browser monitoring which could cause a stack overflow exception.
• For custom instrumentation, the metricName parameter will be honored without needing to set transactionNamingPriority.
• The scriptable installer will now successfully install and uninstall in scenarios where there is a space in the path to the installation files.

Framework Support

• This release of the agent removes support for .NET Framework versions earlier than 4.5. See our community post about this from November of last year, for more details.
• This is not an end of life for the 6.x agents (that support older .NET Frameworks), which will continue to work and report into New Relic.

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.