.NET agent release notesRSS

New Features

• Feature #672: This release of the .NET agent enables distributed tracing by default, and deprecates cross application tracing. (#700)
• Feature #671: The maximum number of samples stored for span events can be configured via the spanEvents.maximumSamplesStored configuration in the newrelic.config or the NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED environment variable.(#701)
• Feature #703: Increases the default maximum number of samples stored for span events from 1000 to 2000.(#705)
• Feature #532: Adds environment variables for log level NEWRELIC_LOG_LEVEL and directory NEWRELIC_LOG_DIRECTORY to allow better control of logs for the agent and the profiler. (#717)

Fixes

• Fixes issue #707: In 8.40.1 SQL explain plans are not being captured for parameterized SQL statements. (#708)
• Fixes issue #502: Agent encountering serialization error (#715)
• Fixes issue #679: Update gRPC libraries from 2.35.0 to 2.40.0 to reduce installation size (#721)

Deprecations/Removed Features

• Cross application tracing is now deprecated, and disabled by default. To continue using it, enable it with crossApplicationTracer.enabled = true and distributedTracing.enabled = false.
• Issue #667, 668, #669: previously deprecated agent configuration options are now disabled. See the migration guide for details.
• Issue #666: previously deprecated agent APIs have been removed, and disabled in the Agent. Disabled APIs will log a warning when invoked by old versions of the .NET agent API. See the migration guide for details. (#687)
• Issue #702 Deprecate instrumentation for Castle.Monorail (#710)

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

Fixes

• Fixes issue #627: Grpc channel shutdown can cause license_key is required error message. (#663)
• Fixes issue #683: Requested stack trace depth is not always honored. (#684)

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

New Features

• Feature #611: Capture HTTP request method on transactions in the AspNetCore, Asp35, Wcf3, and Owin wrappers.
• Feature #580: Send initial app name and source in environment data. (#653)
• Adds support for capturing stack traces for each instrumented method in a Transaction Trace.
  • This feature is disabled by default.
  • You can enable the capture of stack traces by setting either maxStackTrace to any value greater than 1. This value will only be used to determine if stack traces are captured or not despite the name.
  • The following are the default settings for stack traces. These can be changed using the newrelic.config:
    • A maximum 80 stack frames are reported per stack trace.

Fixes

• Fixes issue #639: RabbitMQ instrumentation can delete user headers from messages. Thank you @witoldsz for finding and reporting this bug. (#648)

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

Fixes

• Fixes issue #485: SendDataOnExit configuration setting will prevent Infinite Traces data sending interuption on application exit. (#550)
• Fixes issue #155: MVC invalid Action for valid Controller can cause MGI. (#608)
• Fixes issue #186: Attribute based Routing (ex WebAPI) can cause transaction naming issues. (#612)
• Fixes issue #463: Handle OPTIONS requests for asp.net applications. (#612)
• Fixes issue #551: Missing external calls in WCF Service. (#610)
• Fixes issue #616: Linux Kudu not accessible when .NET agent presents. (#618)
• Fixes issue #266: Agent fails to initialize and provides no logs when configured with capitalized booleans. (#617)
• Explain plans will be created if transactionTracer.explainEnabled is true and one or both transactionTracer.enabled or slowSql.enabled are true. If transactionTracer.explainEnabled is false or both transactionTracer.enabled and slowSql.enabled are false, no Explain Plans will be created.
• Fixes issue #600: Thread id will now be used in agent logging, even if a thread name has been set. (#626)
• Fixes issue #476: When generating and explain plan MS SQL parsing is matching parts of words instead of whole words
• Fixes issue #477: SQL Explain plans MS SQL parser needs to be able to ToString an object to work with parameterized queries
  • Improves handling serializable types like DateTimeOffset
  • The presence DbTypes Binary and Object will prevent an Explain Plan from being executed. In order to execute an explain plan, the agent must replace any parameters in a query with the real values. Binary and Object are too complex to properly serialize without introducing errors.

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

New Features

• Adds Agent support for capturing HTTP Request Headers.
  • Support included for ASP.NET 4.x, ASP.NET Core, Owin, and WCF instrumentation. (#558, #559, #560, #561)
  • To enable this feature, the new allowAllHeaders configuration setting must be set to true. For more information about this new configuration, visit the agent configuration page.

Fixes

• Fixes issue #264: Negative GC count metrics will now be clamped to 0, and a log message will be written to note the correction. This should resolve an issue where the GCSampler was encountering negative values and crashing. (#550)
• Fixes issue #584: When the agent is configured to log to the console, the configured logging level from newrelic.config will be respected. (#587)

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

Fixes

• Fixes issue #500: For transactions without errors, the agent should still create the error intrinsics attribute with its value set to false. (#501)
• Fixes issue #522: When the maxStackTraceLines config value is set to 0, the agent should not send any stack trace data in the error_data payload. (#523)

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

Fixes

• Fixes issue #22: Agent causes exception when distributed tracing is enabled in ASP.NET Core applications that use the RequestLocalization middleware in a Linux environment. (#493)
• Fixes issue #267: On Linux, the profiler fails to parse config files that start with a UTF-8 byte-order-mark (BOM). (#492)
• Fixes issue #464: Distributed tracing over RabbitMQ does not work with RabbitMQ.Client versions 6.x+ (#466)
• Fixes issue #169: Profiler should be able to match method parameters from XML that contain a space. (#461)

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

New Features

• Add GetBrowserTimingHeader(string nonce) overload.
  • This allows sites with a Content-Security-Policy that disables 'unsafe-inline' to emit the inline script with a nonce.

Fixes

• Fixes Issue #394: agent fails to enable infinite tracing in net5.0 docker images.

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

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 or higher agent versions.

Download URLs

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

• .NET Framework

New Features

• CI/Deployment moved to GitHub Actions
  This release is functionally identical to version 6.26.0. We have migrated our CI and deployment process for the 6.x agent to GitHub Actions, and this release validates that this process is working correctly. There is no need to upgrade from 6.26.0 to 6.27.0.

Support statement

New Relic recommends staying current with the latest 6.x version. The .NET Agent 6.x updates include only security-related fixes. Active development of features and other bug fixes is no longer supported.

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.