.NET Agent 6.0.0.0 Release Notes

Released on: 2016, September 14 - 14:00—Download

New Features

Async support in .NET.

The .NET agent now provides out-of-the-box asynchronous framework instrumentation. With the standard async-await pattern, as introduced in .NET 4.5, calls to async methods can return while work being done in the called method is still in progress. For supported libraries and methods monitored with async custom instrumentation, the .NET agent observes this in-progress asynchronous work and waits for it to complete before recording timings.

To take full advantage of features in this release please see this document.

Fixes

  • Fixed method segment naming for transaction traces to ensure consistency. For previous versions of the agent with async mode enabled, some method segments in transaction traces had inconsistent categories and different method formatting. Fixed these to make them consistent in async supported agent. Category: DotNet, Slowest components: Type.Method().

Upgrading

The .NET Agent team is very excited to release v6.0 of our agent. v6.0 does not have a lot of changes from v5.22. In fact, the primary change is that the new Async code base is now defaulted to on. The reason the agent gets a major version number increase is that this new code base is the one we are now building all our new features upon. With v6.0 and its new code base released, the team is looking forward to adding many exciting new capabilities in the coming months.

Thank you for your suggestions on the Async enhancement and your patience.

1 Like

Hopefully the first will be proper support for TransactionError? :stuck_out_tongue_winking_eye:

@stefan_garnham I’m assuming you’re referring to a previous issue or feature request. Can you provide a link to a post or specific details? If we need to file a bug or feature request, we’d like to do so sooner rather than later. :slight_smile:

Well, at the moment the .Net APM agent does not support TransactionError events. Which is why the Error Analytics view is not rich enough for us .Net consumers.

I had mentioned this previously :stuck_out_tongue_winking_eye:

1 Like