.NET agent release notesRSS

New Features

• Agent overhead is reduced for transactions composed of an unusually large number of small activities.

Fixes

• Enhanced low-level logging to improve supportability.
• Fixed a problem with new installs using the Thin Installer where false permission errors could be reported.

Upgrading

• Follow standard procedures to upgrade 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

• In some cases, the trace breakdown table overreported segment times. This happened when these three conditions were met, 1. instrumentation occurred through custom XML files, 2. the segment name was overridden, and 3. the segment contained child segments.

Upgrading

• Follow standard procedures to upgrade 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 preventing injection of a mscorlib reference into every module.

Upgrading

• Follow standard procedures to upgrade 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

• The .NET agent no longer supports Windows Server 2003. Applications running on Windows Server 2003 will be required to use .NET agent version 6.11 or lower. For more information, get support at support.newrelic.com or download the agent at https://download.newrelic.com/
• Reduced overhead of the agent for transactions that contain many segments.
• Reduced performance overhead for instrumented methods. Low latency, high-throughput applications may also see a reduction in CPU overhead.
• Reduced the overhead associated with method JITs. This will reduce the overall startup time and memory footprint of instrumented applications.

Fixes

• Methods associated with wrappers that have been disabled due to too many exceptions are no longer instrumented by the default wrapper. The previous behavior could result in orphaned metrics and a potential degradation in performance.

Upgrading

• Follow standard procedures to upgrade 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

• A new configuration option to supply a proxy URI path has been added to the newrelic.config file. See proxy-uripath.

Fixes

• Resolved issue where service.request parameters, if present, were being transmitted to New Relic as part of an error analytics event.
• Fixed issue that could cause a SerializationException and cause metrics to be dropped.
• Fixed bug that would cause performance degradation for deeply nested segments.
• Fixes issue where scoped metrics would be dropped from an initial custom transaction when a second custom transaction was created. Impacts transaction created using the BackgroundThreadTracerFactory or the OtherTransactionWrapper via XML.
• Setting slowSql in newrelic.config to 'false' will now turn off slow SQL traces in the agent. This setting defaults to true. Server configuration values for this setting will override the value in the newrelic.config file.
• Removed the generation of unscoped metrics in cases where a transaction was not available. The generation of these metrics has been found to have a noticeable negative performance impact, particularly to low-latency/high-throughput applications. This impact typically shows up as a drop in throughput and higher CPU overhead. The vast majority of these metrics are not visible unless added to a custom dashboard. Datastore and External metrics, however, were visible on their respective pages and will no longer be displayed unless associated with a transaction.
• Fixed an issue when end-user monitoring is enabled that could cause some UTF-8 characters to get corrupted.
• The .NET agent now sends up the databaseDuration and externalDuration attributes when the value is 0.

Upgrading

• Follow standard procedures to upgrade 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 "Query plan threshold" from server settings was being incorrectly interpreted. This caused a spike in SQL traces as well as explain plan executions for clients using server configuration.
• Fixed a potential memory leak when an update to agent configuration is performed.

Upgrading

• Follow standard procedures to upgrade 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 where a SerializationException message is generated in New Relic log during monitoring of asychronous calls.
• Resolved issue where newrelic.config changes were not being picked up by the agent.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

New Features

• With this release, the agent reports error analytic events. The event type is called TransactionError, and it powers the Error Analytics in APM feature. The error events are also available through New Relic Insights.
• For applications with high volume, low latency characteristics, performance has been improved resulting in lower agent overhead and greater application throughput.
• Performance improvements, related to the capturing of slow transaction traces, have been made to the agent which should result in less CPU overhead.

Fixes

• A bug was fixed which could cause the agent to shut down immediately at startup if a specific network error was encountered. The agent would then not restart until the application was restarted. The agent now retries network connection attempts indefinitely at startup until success is achieved, in all cases.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.

New Features

• Added instrumentation for RabbitMQ client versions 3.5 and above. For more information on which RabbitMQ operations are instrumented, see: Compatibility and requirements for the .NET agent.
• Added instrumentation for Couchbase client versions 2.x. For more information on which Couchbase operations are instrumented, see: Compatibility and requirements for the .NET agent.

Fixes

• Fixed a bug where MS SQL Server instrumentation would generate exceptions and disable itself when a connection string contained a port number.

Upgrading

• For upgrade instructions, see Upgrade the .NET agent.
• If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.