• EnglishEspañol日本語한국어Português
  • 로그인지금 시작하기

.NET agent release notesRSS

January 25, 2017
.NET agent v6.7.67.0

New Features

Fixes

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

Upgrading

January 12, 2017
.NET agent v6.6.5.0

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

January 5, 2017
.NET agent v6.5.29.0

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

December 19, 2016
.NET agent v6.4.21.0

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

November 9, 2016
.NET agent v6.3.123.0

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

October 13, 2016
.NET agent v6.2.26.0

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

September 29, 2016
.NET agent v6.1.48.0

New Features

  • Added ability to configure the use of Gzip compression instead of Deflate (the default) when sending data to New Relic. This can be useful in cases where DLP software requires Gzip compression for verification.
  • Added ability to configure the use of PUT instead of POST (the default) for sending data to New Relic. This can be useful in cases where DLP software requires PUT for verification.

Fixes

Upgrading

September 14, 2016
.NET agent v6.0.0.0

New Features

Async support in .NET.

The .NET agent now provides out-of-the-box asynchronous framework instrumentation. With the standard async-await pattern, as introduced in .NET 4.5, calls to async methods can return while work being done in the called method is still in progress. For supported libraries and methods monitored with async custom instrumentation, the .NET agent observes this in-progress asynchronous work and waits for it to complete before recording timings.

To take full advantage of features in this release please see this document.

Fixes

  • Fixed method segment naming for transaction traces to ensure consistency. For previous versions of the agent with async mode enabled, some method segments in transaction traces had inconsistent categories and different method formatting. Fixed these to make them consistent in async supported agent. Category: DotNet, Slowest components: Type.Method().

Upgrading

August 31, 2016
.NET agent v5.22.6.0

New Features

Fixes

  • Fixed a spelling error in NewRelic.Providers.Wrapper.WebServices.Instrumentation.xml.
  • Removed duplicate instrumentation out of CoreInstrumentation.xml.
  • Improved transaction handling for rare cases where a segment cannot be associated with its parent. This scenario can occur in applications with complex threading architectures and would previously cause the entire transaction to be dropped. The transaction will now be retained but the orphaned segment and children will be excluded. A warning log message including specifics will be generated for further troubleshooting.

Upgrading

August 23, 2016
.NET agent v5.21.74.0

Fixes

Upgrading

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.