.NET agent release notesRSS

New Features

• Users can now set a customized host name to be displayed in the APM UI via the newrelic.config file or an environment variable. For more information, visit https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-...
• [.NET Framework] Added the ability to enable the agent from the local newrelic.config file for all non-IIS hosted .NET Framework applications. Additional information can be found at: https://docs.newrelic.com/docs/agents/net-agent/additional-installation/...

Fixes

• The profiler now honors the log level configuration setting that is set in the app-local newrelic.config file.

Other Information

• After November 7th, 2018 the Core_20 directory will be removed from the download site. This folder currently contains an outdated version of the .Net Core agent. The most up-to-date version of the .NET Core agent can be found in inlatest_release directory.

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

New Features

• Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.
• To enable distributed tracing, see .NET Agent configuration.

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 support for capturing request.uri attribute for WCF services when available.
• [.NET Core] SQL query parameter values can now be captured on Slow SQL Traces on Linux.

Fixes

• Fixes an issue where errors set to be ignored through configuration were not being ignored.
• Fixes an issue where running the thread profiler can cause an application to terminate.
• Fixes an issue where transaction events could be dropped.
• [.NET Core] Fixes an issue for .NET Core applications running on Linux when serializing slow SQL trace and explain plan data for transmission to New Relic. Previously, the following exception would be seen in the agent logs: NewRelic ERROR: System.PlatformNotSupportedException: Operation is not supported on this platform.

Notes

• We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly.
  • All downloads for the current version of the agent can be found in the latest_release directory on the download site.
  • Historical versions can be found in the previous_releases directory.

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

• SQL query parameter values can now be captured on Slow SQL Traces. This feature can be enabled with the new configuration option datastoreTracer.queryParameters. The transactionTracer.record_sql configuration option must also be set to raw. See documentation here. This feature should be used with caution as it can lead to the capture of sensitive data. High-security mode prevents the use of this feature. Windows support only. Linux support coming soon.
• [.NET Framework] Adds support for tracking async transactions when .ConfigureAwait(false) is used from async controller actions in ASP.NET MVC applications.
• [.NET Core] Adds support for .NET Core 2.1. Support for .NET Core 2.1 requires at least CLR version 2.1.3 and tiered compilation must not be enabled.

Fixes

• [.NET Core] Fixes issue where status code based errors would be reported instead of the actual noticed Exception. This most commonly occurred with errors noticed in the ExceptionHandlerMiddleware (app.UseExceptionHandler(...)).
• Fixes an issue where only the first request parameter is captured when request.parameters.* attributes are added to an include list.

Notes

• We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly.
  • All downloads for the current version of the agent can be found in the latest_release directory on the download site.
  • Historical versions can be found in the previous_releases directory.

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

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