.NET agent release notesRSS

Fixes

• Fixed an issue where the response time of a web transaction could be misreported when making asynchronous external calls whose duration extended beyond the time the web transaction response ended.
• Fixed an issue when using OpenRasta instrumentation where the full URL could be captured on instrumented requests. This may have resulted in query strings being collected which can contain sensitive information. See security bulletin NR19-01.
• Fixes an issue with auto-instrumenting RestSharp and Couchbase driver calls involving non-public collection types.

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 an issue where stack traces for custom errors outside a transaction were not visible in the Error Analytics UI page.
• Fixes an issue with auto-instrumenting MongoDB driver calls involving non-public collection types.
• Fixes an issue with reporting the same transaction multiple times.

New Features

• Improved performance when serializing metrics prior to sending to New Relic.
• Improved SQL-related database instrumentation performance.

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 a bug in SQL-related database instrumentation that potentially causes a CPU spike. This bug appeared in the agent version 8.9.130.

New Features

• [.NET Core] Adds support for .NET Core 2.2.
• Adds support for ASP.NET Core 2.2.
• Improves the performance of cross application tracing.

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

Added auto instrumentation to prevent associating Serilog PeriodicBatchingSink activity with an application’s transactions.

New Features

Added API support for manually creating and accepting distributed tracing payloads.

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 potential memory leak when Distributed Tracing is enabled.
• Fixes an issue where a NullReferenceException is logged for certain data stores (MongoDB and Couchbase) when distributed tracing is enabled.
• Fixes an issue where a transaction start time is incorrect when an error has been reported.

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.

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.