.NET agent release notesRSS

New Features

• ASP.NET, MVC, and Web API instrumentation has been greatly improved. We now time each of the lifecycle events to help diagnose problematic areas of the .NET lifecycle such as session state lock contention. MVC and WebAPI should now properly wrap the time spent in controller actions inside the proper segment.
  • We should now see far more exceptions that occur in your application, with full stack traces. The caveat here is that your error rate may appear to spike after upgrading and you may need to add some additional configuration to ignore more errors (or adjust error rate thresholds).

Fixes

• Fixed a bug where WebAPI exceptions didn't contain stack traces.
• Increases the number of places during the ASP.NET Lifecycle that New Relic API methods that modify the transaction (like SetTransactionName) can be used.
• Provides support for instrumentation of methods on generic class types.
• Fixed a bug that would sometimes cause IIS to get into a bad state under certain load conditions where it would stop serving requests. This could be identified by an exception from IIS around System.Web.HttpApplication.PipelineStepManager.ResumeSteps.

Other

• MVC2 applications will no longer generate MVC-specific segments or have MVC route-based transaction names.
• Thread profiles will no longer put threads into the Web Requests thread bucket (the Other bucket will be used instead)

New Features

• The .Net Agent now reports Insights Transaction Events for transactions that are errors. New queryable attributes: errorType and errorMessage are reported on these events, providing a reliable way to filter out error transactions in your Insights queries.

Fixes

• Fixes a bug where breakdown tables wouldn't include external calls.

Fixes

• Fixes a bug where setting transaction trace threshold from the New Relic UI would cause it to revert to default.
• Fixes a bug where the cross application map would sometimes show the wrong color (apdex) line between nodes.
• Fixes a bug where the New Relic tray application would report IIS 7+ as not running if one of the application pools was stopped.

New Features

• The .NET agent now gives you additional information for requests from synthetic monitors. More transaction traces and events give you a clearer look into how your application is performing around the world.

New Features

• Added support for agent-side creation of application labels and categories via newrelic.config or the NEW_RELIC_LABELS environment variable.

  Labeling enables organization of applications with labels and categories. The APM UI will use these labels and categories to group, filter and organize all your applications in a meaningful way; this is particularly useful if you have many applications. For more information, see Labels and categories.

Fixes

• Fixes a race condition that could lead to a small amount of missing data and in some rare cases, excessive CPU utilization. Most likely to occur with WCF applications under heavy load.
• Fixes a bug where turning on high-security mode and turning off SQL would result in receiving obfuscated SQL.

Fixes

• Disables automatic instrumentation of Microsoft Azure Websites SCM service site.

Improvements

• Adds functionality to the system tray application that will collate information commonly asked for by New Relic support and upload it to S3 when instructed to by the user.
• Response.status is now reported by default in the latest version of the .NET agent on all Insights Transaction events. Previously, this required a configuration change, but now the user simply has to update their agent to the latest version.

Fixes

• Fixes a bug that would cause a failure to connect to New Relic when local high security was enabled and ssl was disabled. Now you will successfully connect with SSL in this scenario.
• Fixes a bug where ignoring a status code for error reporting would sometimes not work correctly and the error would still be reported.
• Fixes a bug where CPU usage sometimes increased with agent version 3.6.177.
• Fixed a bug where applications running older agents making requests of applications running newer agents would sometimes cause the application running the newer agent to drop the transaction.

New Features

• Flexible capturing of attributes

  You can now fine tune the attributes the .NET agent sends to New Relic. For more information, see .NET agent attributes

Fixes

• Fixes a bug where external requests that occurred outside of a transaction were generating error traces when the response code from the external request was an error.
• Fixes a bug where environment wasn't showing up correctly in the New Relic UI.

Notes

New Features

• This release enhances cross application tracing with a visualization of the cross application calls that a specific Transaction Trace is involved in. The new visualization helps you spot bottlenecks in external services within Transaction Traces and gives you an end-to-end understanding of how the transaction trace is used by other applications and services. This leads to faster problem diagnosis and better collaboration across teams. All agents involved in the cross application communication must be upgraded to see the complete graph. You can view cross application traces from in the Transaction Trace drill-down.

Fixes

• Fixes a problem where a transaction may not be correctly recorded if the application is using WCF services. In this case, one of two exception types may appear in the agent log file: a Null Reference Exception or an Object Disposed Exception.