April 13, 2016
.NET agent v5.18.36.0
New Features
- Async mode: Instrumentation of NServiceBus is now enabled when the AsyncMode flag is true.
- Async mode: Added support for Microsoft Message Queue (MSMQ) instrumentation when Async mode is enabled.
- Async mode: Microsoft Enterprise Library officially supported when Async mode is enabled.
Fixes
- Fixed a bug where ASP.NET 4.5+ applications would not get transactions for requests that had invalid query stings (such as "myPage.aspx?test=").
- Fixed an issue where metrics from database calls using Enterprise Library would display as from vendor "Other." The metrics should now show the appropriate supported vendor (Oracle, MsSql, etc.).
- Fixed a bug that prevented SqlCommand.ExecuteNonQuery commands from being instrumented with the default instrumentation xml files.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
April 4, 2016
.NET agent v5.17.59.0
New Features
New Features
- Added support for Stack Exchange Redis strongly named assembly: StackExchange.Redis.StrongName.
- Added support for the "CustomSegmentTracerFactory" custom instrumentation option. See docs for example usage.
- Async mode: Added support for NpgsqlCommand asynchronous methods (such as ExecuteReaderAsync) when the agent is in Async mode.
- Async mode: Explain plans for MS SQL and MySQL commands are now available when the agent is in Async mode.
Fixes
- Async mode: Fixed a bug that prevented SQL activity from being recorded in transactions.
- Fixed a bug where the incorrect namespace of the default asynchronous wrapper was used. The incorrect name was "NewRelic.Agent.Core.Wrapper.DefaultWrapperAsync" and is now "NewRelic.Providers.Wrapper.CustomInstrumentationAsync.DefaultWrapperAsync". Any customers that had created a custom instrumentation file and put the incorrect name in it as a workaround should change it to the correct name.
- Duplicate custom parameters will now be logged as Debug level, providing a minor performance improvement.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
March 11, 2016
.NET agent v5.16.71.0
New Features
- Async mode: Custom instrumentation is now supported for both synchronous and asynchronous methods when async mode is enabled, however; the metricName and transactionNamePriority elements will not be respected. This is coming in a future release. Please see our custom instrumentation documentation for details.
Fixes
- Changes the log messages for when a wrapper / method combination needs to be shut down. The new message provides more information and clarity around the shutdown event.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
February 24, 2016
.NET agent v5.15.64.0
New Features
- Async mode: Added support for SqlCommand method ExecuteReaderAsync, ExecuteScalarAsync, ExecuteNonQueryAsync, and ExecuteXmlReaderAsync.
- Async Mode: Added support for SQL Traces on slow SQL commands when the agent is in async mode.
- Async mode: Adds support for synthetic transaction tracing when the agent is in async mode.
- Async Mode: Added instrumentation for System.Data.SqlClient.SqlDataReader ReadAsync and NextResultAsync methods. Note that, for performance reasons, this instrumentation is disabled by default in the SqlAsync instrumentation xml file.
Fixes
- Fixed a bug where the agent erroneously treated HTTP headers as being case-sensitive, causing CAT to not work under certain conditions.
- Fixed a bug where the agent rejected custom events if any attribute had a null value.
- Async mode: Fixed a bug that caused some datastore activity to be missed.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
February 9, 2016
.NET agent v5.14.43.0
New Features
- Async Mode: Added Agent API support.
- Async mode: Instrumentation for synchronous SQL commands is available when the agent is in async mode.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
January 21, 2016
.NET agent v5.13.30.0
New Features
- Async mode: The .NET agent now reports CPU and Memory usage metrics which will show up on the APM Application Overview page.
- Async mode: Basic support for Redis and MongoDB are available when the agent is in async mode.
Fixes
- Fixed a bug that prevented Cross Application Tracing from working between Java and .NET applications.
- Fixed a bug where turning on High-security mode did not prevent custom events from being created via the agent API. For additional information regarding High-security mode, please refer to our public documentation: https://docs.newrelic.com/docs/accounts-partnerships/accounts/security/h...
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
January 7, 2016
.NET agent v5.12.13.0
New Features
- Async Mode: Added automatic Browser Monitoring support.
Fixes
- Async mode: Fixed a bug where using HttpClient with a BaseAddress would result in transactions being lost or corrupted.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
December 16, 2015
.NET agent v5.11.53.0
New Features
- Async mode: The .NET agent now has an optional async mode which provides a look at the agent's asynchronous framework instrumentation as it becomes available. As of this release, asynchronous instrumentation for System.Net.Http.HttpClient and System.Net.HttpWebRequest are available when the agent is in async mode. Please note that activating async mode disables some functionality within the .NET agent. More details and instructions are available here: https://docs.newrelic.com/docs/agents/net-agent/features/async-mode-net
Improvements
- Added new log for cases where the .NET Agent cannot inject Browser Agent
Fixes
- Fixes an issue where intermittent connection issues would cause the Agent to shut down until the process was restarted.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
December 1, 2015
.NET agent v5.10.59.0
Fixes
- Fixed a bug where IIS applications using a classic pipeline app pool would sometimes not report transactions.
- Fixed a bug where clicking on the transaction name from an error trace would not take you to the correct transaction page.
- Fixed an Agent API bug that caused the IgnoreApdex to not actually ignore a transaction for apdex calculations.
- Fixed a bug that would sometimes cause transaction data to be lost if the Cross Application Tracing feature was enabled.
- Fixed a bug that sometimes caused agent environment info to be incomplete.
- Fixed a bug where configuring the agent to ignore HTTP sub-status codes (such as 403.1) would result in an exception.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.
November 5, 2015
.NET agent v5.9.74.0
Fixes
- Fixes an issue where if a customer was using the default proxy and not specifying one in the New Relic configuration for the Agent the default would not be used potentially causing HTTP status code 504 to be thrown when communicating with the New Relic collectors.
- Fixes an issue where cross application tracing would slow down in environments using WFC with extremely high throughput.
Upgrading
- For upgrade instructions, see Upgrade the .NET agent.
- If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents for a list of major changes to the .NET agent.