.NET agent release notesRSS

Notes

Fixes

• Fixed a very rare race condition that could cause a monitored application to get into a bad state and start consuming as much CPU as possible (across multiple threads).
• Fixed a bug that would sometimes cause a TypeLoadException when using the New Relic API.
• Fixed a crash that would occur if the agent failed to connect to our servers due to SSL issues when running under IIS7 integrated mode.

New Features

• Adds a new utility (New Relic Status Monitor) that provides a quick way to give feedback on what the .net agent has instrumented just after installation. The tool also provides a quick way to diagnose and troubleshoot issues with instrumentation or with the agent that are normally obscured form the users view.

Improvements

• Fixes an issue in the coreinstrumentation.xml file where an overload for Oracle.DataAccess.Client.OracleCommand.ExecuteReader was not getting instrumented.

Notes

Fixes

• Fixes cleanup of Component Object Model (COM) registration.
• Fixes ability of agent to monitor partially-trusted .NET applications.

Improvements

• Removes comments from the newrelic.xml file and provides a link to the living docs to provide more information on configuring the agent

Notes

New Features

• Added ability to enable/disable various parameter information via agent configuration. This includes the default setting to not capture a username from the security principal associated with a web application.

Fixes

• Fixes instances where the AgentEnabled setting was set to false and the NewRelic.Agent.IL.dll was not getting unloaded from the process. No code was ever executed from the module when the agent was disabled but the module needed to be unloaded so that the process would correctly reflect the actual modules that were being used.
• Fixes an issue where the user could not override the default naming of a transaction using the agent API.

Notes

New Features

• Adds a new API method that can be used to disable Auto or Manual Real User Monitoring (RUM) script injection on a per page basis. Simply call NewRelic.Api.Agent.NewRelic.DisableBrowserMonitoring(); in your view to disable RUM scripts for that page.
  See: https://newrelic.com/docs/dotnet/AgentApi for more information.

Improvements

• Adds Cross Application Tracing for web request calls that use System.Net.WebClient
• Adds Cross Application Tracing for all Traced Errors that happen on the external applications

Fixes

• Addresses an issue where enabling query explain plans on applications using MySql sometimes caused connection leaking.
• Correctly strip forward slash from the category name in AgentAPI's SetTransactionName method.

Notes

New Features

• Adds Cross Application Transaction Trace linking so that in SOA (service-oriented architectures), all applications that are instrumented by a New Relic agent and that communicate with each other via http will now "link" transaction traces with the applications that they call and the applications they are called by. This change helps improve the correlation of performance between services and applications.

Fixes

• The installer should now do a better job of cleaning up bad install states. We are uncertain how users get into such a state, but now it is less problematic when it does occur.

Notes

New Features

• New (not update) installations of the .NET Agent will default to using secure communications (HTTPS) between the agent and the New Relic server.
• Agent logging improvements. We have improved the clarity of logging messages, adjusted logging levels to be more appropriate, and increased logging performance.
• Adds a 'X-NewRelic-ID' header to all outbound http requests. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'crossApplicationTracingEnabled=false' in the configuration element of the newrelic.xml file.

Fixes

• Fix crash in NewRelic.Agent.IL.dll caused by uninitialized data.
• Fix potential metric grouping issues associated with HTTP redirects.
• Fix confusing error message in the Diagnostic tool when the Application Event Log is at least 90% full.
• Fix potential null de-reference in unmanaged dll.

Notes

New Features

• Extends the uri reported in the external call labels in transaction traces so that users can see both the host and the resource being called.

Improvements

• Rewrote the installer.
• You no longer need to uninstall before re-installing the agent. You can simply run the new installer and it will upgrade your old install.
• The installer no longer requires administrative rights at start to complete successfully. It will ask for elevation (on newer OSs) when needed and give reasonable error messages when it doesn't have enough permission (on older OSs).
• If you instrument non-IIS applications you should no longer manually set environment variables manually. Instead, during install choose the "Instrument All .NET Applications" feature. If you have already installed run the installer again and choose "Change".
• Configuration and log files are now stored in %ALLUSERSPROFILE%\New Relic.NET Agent\ instead of Program Files.
• The API is now optionally installed and should only be needed on development machines and build servers.

Fixes

• Restores request queuing metrics being reported by the agent - they will now appropriately appear in the overview graphs

Notes

New Features

• Adds Real User Monitoring (RUM) auto instrumentation for all .net MVC versions

Fixes

• Fixed an issue that would cause certain methods to not to be instrumented correctly including but not limited to Oracle.DataAccess.Client.OracleCommand.ExecuteReader.

Notes

Fixes

• Addresses an issue where the Real User Monitoring (RUM) footer was being injected outside of the body close tag in Web Forms applications, creating invalid markup. Also improves the performance of the auto instrumentation of RUM in Web Forms applications.
• The Apdex score (Satisfied, Tolerating, Frustrating) was being incorrectly reported for Key Transactions, and was also skewing the overall Apdex score.