.NET agent release notesRSS

Notes

Improvements

• Removed unnecessary instrumentation of an ASP.NET pipeline execution method.
• When automatically inserting the browser monitoring javascript, the agent now assures that a charset meta-tag continues to fall within the first 512 bytes of the document. Prior to this fix, insertion of the javascript may have pushed the charset meta-tag past the first 512 bytes, which would cause the character set not to be set, resulting in the browser setting the default to something that may not be what the developer intended.

Fixes

• Fixes an issue where the Real User Monitoring Javascript was being injected into the page more than once because the response stream was being chunked.
• Fixes a problem where Unicode characters were not being correctly written to the page in some cases when Browser Monitoring was enabled in the agent.
• Fixes an issue where log files from the .NET Agent for Azure Websites were not being put in the correct location.
• Calling SetTransactionName via the NewRelic API will now behave correctly in background transactions.
• Fixes a bug where browser monitoring data was not captured when using Server-Side Configuration and Enterprise Security.
• Fixes an issue where when disabling Real User Monitoring in the New Relic UI the value set was not properly overriding the local configuration on the server.
• Fixes an issue where disabling the error collector in server-side configuration did not actually disable error collection by the agent.

Notes

Improvements

• Improves transaction breakdown and transaction trace views by filtering certain .NET Framework methods.
• 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.
• Removes an erroneous error log message related to attempting to instrument RefEmit_InMemoryManifestModule.

Fixes

• 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!

Notes

Fixes

• Fixes a problem where running a thread profile against a 32-bit application fails to complete.

Notes

Improvements

• Reduces overhead cost (CPU and response time) of the agent in some cases.

Fixes

• Fixes an issue where the Agent was not quickly releasing DBCommand when the explain plan threshold had been reached.
• Fixes an instance where a NullReferenceException might happen when the agent would try to record transaction statistics.
• A bug was fixed where the Capture Parameters setting (for Request Parameters) in Server-Side Configuration was not being respected by the agent.

Notes

Improvements

• We now add custom parameters to project Codename "Rubicon."

Notes

Fixes

• Fixes an issue where browser traces were not showing up in New Relic.

Notes

Improvements

• Adds Windows Server Monitoring to the New Relic Azure Cloud Services nuget package. Now when users add or update the nuget package on their cloud service projects and deploy they will begin getting all of the data and benefits of Windows Server monitoring. Thanks Steven Kuhn for the contribution!
• Browser monitoring has been enhanced to allow for easier inclusion of features in client-side profiling. The agent now only injects javascript in the page header or, in the event that no head section exists, immediately before the opening body tag. In addition, the algorithm for identifying the insertion point has been improved.

Fixes

• Fixes a bug during metrics harvest where a race condition might throw an exception.

Notes

Fixes

• Additional fixes for cases where status codes were not correctly being ignored when they should have been.

Notes

Fixes

• Fixed a bug where transactions were sometimes not being named.
• Fixed a bug where status codes were not correctly being ignored when they should have been.