.NET Agent 2.24.218.0

Notes

Due to the performance impact, adding "NewRelic_BrowserTimingHeader" and "NewRelic_BrowserTimingFooter" to manually-instrument browser monitoring (RUM) has been deprecated. The recommended method for manual instrumentation is to use the New Relic .NET Agent API. See the documentation page: https://docs.newrelic.com/docs/dotnet/real-user-monitoring-in-net for details.

Reduced the overhead of the agent through improved targeting of instrumented methods.

Fixes a bug where sometimes thread profiles would not display properly after being collected successfully.

Fixes an issue where System.Data.SqlClient.SqlConnection.Open() metric was being removed from traces making it more difficult for users to gain visibility into how many database connections each transaction in their app was opening.

Fixes a bug where the agent wouldn't increment the total errors count for errors reported via the API that occurred outside of a transaction.

NuGet

Fixes an issue where after deploying Windows Server monitor using the nuget package to Windows Azure the service will be in a stopped state. The Windows Server monitor will now start after deployment. Thanks Steven Kuhn for the contribution!

Was this page helpful? *

Yes

No

Great! Help us improve our content by telling us what worked well and what we could do better.

Sorry to hear that. How can we improve this content?

Comments

Note: This feedback form exists solely to improve the quality of our documentation. If you need help with New Relic products or want responses to your questions, please see our support site.