.NET agent release notesRSS

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.

Notes

Fixes

• An unhandled null reference exception has been fixed.
• Fixed a bug that would cause a stack overflow if you tried to instrument a generic method with multiple instantiations.

Notes

Fixes

• Fixes an issue where content-type was being explicitly checked for "text/HTML." In some frameworks, such as NancyFX, the charset was being added to the content-type before the New Relic HTTP module was loaded which caused the explicit check to fail and the RUM header and footer to not be added to the pages.
• Fixes an issue when the application results in a status code 404 or greater the metrics would be reported for the page not found instead of recording metrics for the 404 itself. This change also addresses an issue where assets such as png, css, js and so on would have metrics recorded for each individual asset instead of rolling them up into the appropriate asset group, such as *.png or *.css. Finally there were other metric grouping issues fixed where metrics were being named the custom route (such as /products/1) on some applications instead of using the name of the code asset that was doing the work to create the page (such as /products/productstemplate.aspx).
• Corrects functionality of the Status Monitor for IIS6 installations and applications running under sites other than DefaultWebSite.

New Features

• A thread profiler has been added to the .NET agent. The thread profiler is a low-impact profiling tool that can be used in production to identify bottlenecks in an application.

Improvements

• Improves the logic around the RUM response filters which reduces the overall overhead of the .NET agent.
• Log files now have windows style line endings so they display correctly in notepad.exe.
• The status monitor tray application will now prompt for elevation on launch rather than error at runtime when it doesn't have correct permissions.
• Azure Cloud Services nuget package : Modified the package so that when installing a new version it will attempt an upgrade if an existing agent is installed. (This feature requires Nuget v.2.6 which prompts the user to overwrite existing / modified files - the newrelic.cmd must be overwritten to apply the new commands on the cloud service)
• Azure Cloud Services nuget package : The package now properly cleans up the environment variables out of the csdef when an uninstall or update occurs.
• Azure Cloud Services nuget package : For Worker Roles, the msiexec command in the newrelic.cmd file as been changed so that when the agent is installed it will install it for all CLR based applications.

Notes

Fixes

• Fixed a bug whereby IIS applications with underscore characters in their names were not displayed correctly in the Status Monitor.
• Fixed a bug whereby users could not view the log file for some IIS applications in the Status Monitor.

Improvements

• Improved the naming of MVC transactions. Naming to controller/action should be much more reliable now.
• Improved WebAPI support. You should now see Web Transactions grouped by [controller].[action] rather than all WebAPI transactions reporting as System.Web.Http.WebHost.HttpControllerHandler.

Notes

Fixes

• Fixed a bug where external request timing was showing up on the call to WriteHeaders instead of on the Stream Read. The Stream Read has been removed and WriteHeaders should correctly report as being fast. In their place you will now see all the time occurring inside a call to Stream GetResponse.
• Fixed a bug in external request counting that would result in the counts being too high.
• The Original Url custom parameter will now contain the correct value if the application had re-written the Url in the BeginRequest event handler of an HttpModule.
• Fixes an issue on Windows 2003/IIS 6 server where the New Relic Status Monitor was showing no reporting applications and an incorrect error message about IIS being in a stopped state in some cases where apps hosted on the machine were in fact reporting to New Relic.
• Fixed an issue where sometimes our usage of Log4Net would conflict with the user's usage of Log4Net.
• Fixed a bug that would cause some stack traces thrown in the user's application to be truncated.
• Moved some spammy log messages to debug level logging.

New Features

• Improved cold startup time for user applications instrumented by New Relic.
• Added the ability to selectively include or exclude certain application pools from being monitored by New Relic.

Improvements

• Improved error logging of API method calls. If you call an API method at an invalid time or you supply invalid parameters a warning will be logged to the New Relic .NET Agent log file.
• Changed startup logging location from the event log to log file on disk.
• Changed the agent configuration file from newrelic.xml to newrelic.config.