.NET agent release notesRSS

Fixes

• Fixes a problem with parsing method signatures that do not align with ECMA-335 that could cause an application to crash.
• Fixes a problem where third-party libraries that perform assembly-scanning using reflection may encounter TypeLoadExceptions.
• Fixes a problem where the agent may incorrectly report Response Time when custom instrumentation is applied to methods that are called from within an instrumented framework (such as ASP.Net).
• Resolves security issue with how SQL Server handles escaping which could lead to a failure to correctly obfuscate SQL statements. See Security Bulletin NR19-03.
• Resolves issue with not rolling up 30x HTTP response codes which resulted in MGI issues.

New Features

• Adds improved WCF support
  • WCF client task asynchronous programming model (following the task asynchronous pattern) calls are tracked as external calls.

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

• Fixed issue where transactions may not get reported when custom instrumentation is applied to async methods with a void return type. Instrumenting async void methods is generally not recommended and may result in unexpected segment timing as well as the disruption of downstream instrumentation. Please review async limitations online help for alternative approaches.

New Features

• [.NET Core] Adds support for .NET Core 3.0
• [.NET Core] Adds support for ASP.NET Core 3.0
• [.NET Framework] Adds support for .NET Framework 4.8 Early Access build 3694
• Adds official support for Postgres/Npgsql versions 4.0.
  • Supports Sync and Async methods, on .Net Framework and .Net Core running in Windows and Linux.
  • Eliminates duplicate and extraneous datastore metrics and trace segments associated with opening connections to databases (as seen in prior agent versions).
  • Npgsql versions older than 4.0 may also be instrumented, but duplicate and/or missing metrics are possible.
• Adds improved WCF support
  • WCF client calls are tracked as external calls
  • WCF client synchronous and asynchronous programming model (following the begin/end asynchronous pattern) calls are tracked.

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

• [Framework] Improved support for async workloads in self-hosted OWIN applications.
• [Framework] Status code only errors are now noticed in self-hosted OWIN applications.

New Features

• [Framework] Adds support for the following in .Net Framework self-hosted OWIN apps:
  • Microsoft OWIN version 4
  • Distributed tracing
  • Cross application tracing
  • Request parameters capture
  • Request URI capture
  • Introduces single metric creation for HTTP status codes 400 and greater
  • Exception capture from OWIN middleware components

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

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