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.
- 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.
- 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.
- Adds instrumentation support for Oracle's ManagedDataAccess APIs. Now any applications using Oracle.ManagedDataAccess.Client methods will get database instrumentation for those method calls.
- Adds better support for Windows Communication Foundation applications that are hosted by IIS.
- Changed agent logs to use UTC timestamps instead of local server timestamps. This should allow us to resolve customer issues more quickly.
- Changes the agent to depend on .NET 3.5. Your application can still target .NET 2.0, but you must have .NET 3.5 installed on the computer the agent is executing on.
- Fixes an issue where the Agent was not respecting the server side enable error collection setting.
- Removed unnecessary instrumentation of an ASP.NET pipeline execution method.
- Fixes a problem where Unicode characters were not being correctly written to the page in some cases when Browser Monitoring was enabled in the agent.
- Fixes an issue where log files from the .NET Agent for Azure Websites were not being put in the correct location.
- Calling SetTransactionName via the NewRelic API will now behave correctly in background transactions.
- Fixes a bug where browser monitoring data was not captured when using Server-Side Configuration and Enterprise Security.
- Fixes an issue where when disabling Real User Monitoring in the New Relic UI the value set was not properly overriding the local configuration on the server.
- Fixes an issue where disabling the error collector in server-side configuration did not actually disable error collection by the agent.
- Improves transaction breakdown and transaction trace views by filtering certain .NET Framework methods.
- Due to the performance impact, adding "NewRelic_BrowserTimingHeader" and "NewRelic_BrowserTimingFooter" to manually-instrument browser monitoring (RUM) has been deprecated. The recommended method for manual instrumentation is to use the New Relic .NET Agent API. See the documentation page: https://docs.newrelic.com/docs/dotnet/real-user-monitoring-in-net for details.
- Reduced the overhead of the agent through improved targeting of instrumented methods.
- Removes an erroneous error log message related to attempting to instrument RefEmit_InMemoryManifestModule.
- Fixes a bug where sometimes thread profiles would not display properly after being collected successfully.
- Fixes an issue where System.Data.SqlClient.SqlConnection.Open() metric was being removed from traces making it more difficult for users to gain visibility into how many database connections each transaction in their app was opening.
- Fixes a bug where the agent wouldn't increment the total errors count for errors reported via the API that occurred outside of a transaction.
- Fixes an issue where after deploying Windows Server monitor using the nuget package to Windows Azure the service will be in a stopped state. The Windows Server monitor will now start after deployment. Thanks Steven Kuhn for the contribution!
- Reduces overhead cost (CPU and response time) of the agent in some cases.
- Fixes an issue where the Agent was not quickly releasing DBCommand when the explain plan threshold had been reached.
- Fixes an instance where a NullReferenceException might happen when the agent would try to record transaction statistics.
- A bug was fixed where the Capture Parameters setting (for Request Parameters) in Server-Side Configuration was not being respected by the agent.
- 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!
- Fixes a bug during metrics harvest where a race condition might throw an exception.