August 27, 2015
.NET agent v5.4.16.0
New Features
- Added ServiceStack.Redis v3.x and v4.x framework support. The .Net agent now wraps time spent making ServiceStack.Redis API calls, which will appear as Datastore metrics and Transaction Trace segments in New Relic APM.
Fixes
- Fixed a bug that caused web transaction data to be lost if the request contained an invalid "Referer" HTTP header.
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.
August 20, 2015
.NET agent v5.3.90.0
Fixes
- Fixes a bug which caused the .NET Agent to stop reporting intermittently due to an exception raised within the .NET Framework and caught by the Agent.
- Fixes an unhandled System.ObjectDisposedException in the agent.
July 22, 2015
.NET agent v5.2.87.0
Fixes
- Web requests for static resources which are handled by System.Web.Optimization will be named with the requested URL instead of the unmapped route parameters (some previously were named {controller}/{action}/{id}).
July 6, 2015
.NET agent v5.1.72.0
Fixes
- Transactions using MVC attribute routing will show the correct action name instead of "Unknown Action".
June 24, 2015
.NET agent v5.0.136.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
New Features
- Adds an API method for setting the name of the application reported to in New Relic at runtime.
- Adds a configuration option for stopping the agent from reporting automatically when the agent starts up.
- Adds an API method for telling the agent to start reporting at runtime.
Fixes
- Fixes a bug where self-hosted WCF applications would not correctly report on the overview page.
- Fixes a bug where database calls and external calls in a background/async thread would result in a transaction named
*showing up in the Other bucket. - Fixes a bug where apdex was not reported for self-hosted WCF applications.
- Fixes a bug where API calls from an application that didn't have any instrumentation would not report any data.
- SQL object names are more accurately parsed. In particular, table names will be recognized with an expanded set of characters. The agent is able to parse table names with a variety of separator characters and formatting whitespace. For example,
{Table1},[ Table2 ],"Table3"andTable4.
Known Issues
Important
If you are using WebAPI and targeting .NET Framework 4.0 then you may need to opt-in to a .NET Framework 4.5 bug fix in order to continue seeing web transactions! For more information, see WebAPI transactions are missing.
May 20, 2015
.NET agent v4.6.29.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Improvements
- The .NET agent now provides an API for sending custom events to New Relic Insights.
May 14, 2015
.NET agent v4.5.90.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Fixes
- Fixed a bug that sometimes caused thread profiles to be empty.
April 29, 2015
.NET agent v4.4.60.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
New Features
- Web transaction types (seen in tooltips) should now be more meaningful. When you mouse over a transaction, instead of showing Action it will show ASP, MVC, WebAPI, WebService, WCF, etc.
Upgrade Notes
Important
This improvement to transaction naming may impact the transaction names of existing metrics including Key Transactions, Alert on Anything metrics and Insights queries based on transaction names. These would need to be recreated with the new transaction name after the upgrade.
Fixes
- The agent will now fallback to using the proxy configured for the executing user when talking to New Relic.
April 16, 2015
.NET agent v4.3.123.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
New Features
- Non-web transactions can now report Apdex scores. This can be done by marking a non-web transaction as Key Transaction and setting its Apdex threshold to the desired time (in seconds). This allows monitoring and alerting based on this score as well as configuration of thresholds that make sense for long-running or faster background transactions.
Fixes
- Fixed a bug that caused WebApi applications to intermittently throw exceptions under certain conditions.
- Fixed a bug that caused Browser Monitoring autoinjection to increase application memory usage.
- Fixed a bug where attempting to load newrelic.config from web root on a network share would fail.
- Fixed RUM auto-injection for default pages in WebForms applications running on .NET 3.5 or lower in integrated pipeline mode.
- Fixed a bug where sometimes transaction events wouldn't be sent to Insights.
- Fixed a bug where sometimes error traces wouldn't be sent to APM.
- Thread profiles of .NET agent instrumented applications now only contain data in the Other bucket.
March 31, 2015
.NET agent v4.2.185.0
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
New Features
- Customers who use the MongoDB.Driver for .NET in their applications will start to see MongoDB-based transaction segments. Operations will include data querying, aggregation, index creation/retrieval, data insertion/update/removal and bulk write operations. MongoDB datastore transactions will appear in the Monitoring > Databases APM page. The .NET agent uses the 1.10.0 version of the MongoDB Driver for .NET but will report instrumentation for applications using older versions of the driver.
- Provides support for NServiceBus instrumentation, which will appear as transaction segments containing Message Broker, the queue name and the action (such as Produce or Consume). Since NServiceBus can be used for inter-application communication, nodes will also appear within the Cross-Application Tracing map in APM. This release supports NServiceBus 5.0 and later.
Fixes
- Fixes a bug where WCF applications hosted in IIS with compatibility mode disabled would not receive any useful transaction traces.
- Fixes a bug where WCF applications hosted in IIS with compatibility mode disabled would see twice as much throughput and *.svc transactions.
- Fixes a bug where some frameworks (WCF, Umbraco, DotNetNuke, etc.) were not having their transactions named as they were in agent 3.x and instead were getting named by the route.
- Fixed a bug where server-side redirects would cause transactions to be dropped.
- Fixes a bug where default page redirection in IIS classic pipeline mode would cause the redirection to fail and a 404 to occur instead.
- Fixes a bug where an exception could be thrown if the Content Type of an outgoing payload could not be parsed.
- Fixes an issue where the Azure Cloud Services NuGet package will not install on roles that are added as part of a second Cloud Service project.
- Fixes a bug where transactions would sometimes not show up in the UI.
Notes
- There is a known issue in version 4.2.185.0 of the .NET agent which prevents auto-injection in certain specific cases. This issue only affects WebForms websites running in integrated pipeline mode, and only manifests when navigating to the website's root URL.