.NET agent release notesRSS

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.

Notes

New Features

• Provides visibility into Microsoft Message Queue (MSMQ) activity. Within a web transaction, e.g., you can now see whether a message has been sent to a queue, pulled off a queue, peeked at, or if a queue has been purged.

Fixes

• Fixes a crash in the New Relic system tray application that would occur for some users on launch.

Notes

Improvements

Agent-Side High Security Configuration

See https://docs.newrelic.com/docs/subscriptions/high-security

Added new local setting to enable high-security mode. If your account is set to high security in the New Relic UI, you must add the following to your local newrelic.config file under the configuration element: ...

This setting is false by default. Without this property, the agent will stop collecting data when high security is enabled in the New Relic UI.

When set to true, this setting has the following effects:

• Data will not be sent to New Relic unless the agent is using SSL.
• Raw SQL strings will never be gathered, regardless of the value of newrelic.transaction_tracer.record_sql.
• Request parameters will never be captured, regardless of the value of newrelic.capture_params.
• The following API functions will have no effect: AddCustomParameter, SetUserParameters.

Fixes

• Fixes an issue where sometimes applications on the same host reporting to New Relic were not reporting as unique and distinct applications.
• Due to a rare DLL versioning issue, we did not release the NuGet package for Windows Azure Web Sites with our 3.2.113.0 version of the agent. We have fixed the issue and are once again releasing the NuGet package.

Notes

New Features

• Support for Windows Communication Foundation (WCF) now includes:

  • self-hosted (i.e., hosted outside of IIS) services
  • services hosted by IIS whether or not ASP.NET Compatibility Mode is used.
  • service request parameters can be viewed in a transaction trace summary or in an error summary. By default, these parameters are not captured, but can be enabled and filtered in the newrelic.config file using a new parameter group named 'serverRequestParameters'. See the online documentation for more details.

Note: This release is not currently supported for installation via the Azure Web Sites NuGet package. We will be updating that NuGet package at a later time.

Notes

Improvements

• The New Relic .NET Agent Status Monitor should now report more useful error messages for debugging problems. This will allow us to more rapidly act on bug/crash reports in the Status Monitor.
• Messages in the status monitor when checking installation or repairing installation have been improved to be less confusing.

Fixes

• Improves exception reporting in MVC by reporting filtered exceptions. This resolves an issue where turning on custom error pages in an MVC application would cause you to only receive status code errors rather than exception errors. Please remember that you can ignore errors in New Relic either via API call or configuration!
• Fixes a bug where error reporting for transactions was not behaving correctly. You should once again see correct error counts for key transactions.
• Addresses a bug that impacted users who enabled request parameters in the configuration file AND had configured specific parameters to be ignored. For these customers, the ignored parameters were filtered when sent as requested attributes but were still included in the captured URL. Customers with request parameters disabled (the default configuration) or who did not specify any ignored parameters were not impacted by this bug.
• Fixes a bug where sometimes custom instrumentation wouldn't render correctly in the UI. This happened when the metricName in the custom instrumentation file wasn't prefixed with "Custom/". Now the "Custom/" prefix is added automatically if not provided in the file.