.NET agent release notesRSS

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.

Fixes

• Fixes an issue where query string parameters of a request's referrer URL get sent to APM when they should not be. For more information see the security bulletin https://docs.newrelic.com/docs/accounts-partnerships/accounts/security-b...
• The Status Monitor now verifies that the application link points to the New Relic domain before loading the URI in the browser, when the user selects the 'View application in New Relic' button in the Status Monitor.

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

• The agent now collects datastore instance information for Microsoft SQL Server, MySQL, PostGreSQL, Oracle, DB2, and Redis. This information is displayed in transaction traces and slow query traces. Datastore instance details are captured by default. For more information, visit https://docs.newrelic.com/docs/apm/applications-menu/features/analyze-da...
• SQL trace identifiers now use an 8-byte value instead of a 4-byte value so that Data Loss Prevention monitors do not interpret the value as a 9-digit Social Security 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.

New Features

• Transaction events and PageView events now include a common attribute, nr.tripId, which can be used to correlate between them in data returned by Insights. This allows, for example, the browser page load time information and the server page serve time for a web application to be considered together rather than separately.
• A new, scriptable, installer is now available for the .NET Agent. This new installer makes it easier to perform unattended installations of the agent. This installer does not require .NET 3.5. If it is used to install the agent on a 64-bit machine, then both the 32-bit and 64-bit applications will be instrumented. The existing MSI installer is still recommended if you prefer an interactive installation process. For details, see: https://docs.newrelic.com/docs/agents/net-agent/installation-configurati....

Fixes

• Fix an issue where the agent imposes a limitation on throughput for applications using datastores for which instance information is not currently supported.
• Fixed a bug where the database name was not being captured from Microsoft SQL Server connections for the purposes of datastore instance reporting.

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.

Fixes

• Fixed an issue where the agent was not sending data to New Relic upon exit from a very short running application.
• Fixed a bug where parameterized SQL queries might cause an incorrect explain plan to be generated.

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 support for IBM DB2 including slow query support. You'll see relevant breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces.

Fixes

• The enabled attribute of the transactionTracer, when set to false, should disable all transaction trace output. This has been fixed in the .NET agent version 6.2.26.0

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.