.NET agent release notesRSS

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.

Notes

• This is a patch release to address an issue introduced in 2.17.266.0 where resources were not properly disposed, potentially causing a degradation in throughput over time.

Notes

Fixes

• Fixes a bug where sometimes the first transaction after a cold start would be recorded resulting in a notable spike in response time graphs.

Improvements

• Improves running performance and memory consumption of the agent.

Notes

Fixes

• Fixes an issue where the agent was making calls to retrieve the SQL connection's database version unnecessarily. This issue may have caused some customer applications to unnecessarily hold onto database connections.
• Fixes an issue with the harvesting of AnalyticsEvents where a race condition would cause the collection of events to become invalid.
• Fixes a bug where generic exceptions were being reported with generic arguments which made it so they couldn't be ignored.
• Fixed a bug where attempting to add custom instrumentation for a parameterless overload of a method with parameterized overloads would result in all overloads of the method being instrumented.
• Added back support for custom instrumenting methods via parameters='void' in the exactMethodMatcher. It is recommended you use the new way which is to simply leave the parameters attribute off of your exactMethodMatcher, but for those with existing instrumentation files using 'void' parameters that will once again work.

Notes

Fixes

• Fixes a bug where applications were sometimes named incorrectly.

Notes

New Features

• Adds Percentiles and Histograms
• Adds the ability to instrument processes from IIS Express which include Azure Compute Emulator, Web Matrix and Visual Studio. By checking the "Instrument all .NET Applications" checkbox during the installation developers will now be able to get instrumentation on all web applications running as a hosted IISExpress process.

Fixes

• Fixes logging during the installation of the .NET Agent for when the installer looks for an existing license key and on cleanup methods. Now when running installer using msiexec with options /i and /l*v it will now properly report the status of all installer actions in the log output.
• Fixed a bug that would cause a stack overflow if you tried to instrument a generic method with multiple instantiations.

Notes

Fixes

• Resolved an issue where an application with limited permissions could throw an expensive/slow exception repeatedly per transaction causing increased CPU usage and decreased response time
• Resolved a performance issue associated with reading configuration off disk too frequently.
• Resolved several minor performance issues.