There are a few items in the .NET Agent backlog, all of them are good stuff, however we're missing some data points to help us rank them and decide which one to build next.
Therefore, I've put up a survey to gather your feedback: .NET Agent future Survey
A quick explanation about each of the items in there:
In the "Cheap but useful" category, we have:
- Migrate FullTTDetailsTracer to new mode
- In the absence of Smart Instrumentation, one could use FullTTDetailsTracer to gain visibility into one's application. Currently it's only available in Legacy mode, therefore restricting its potential.
- Hotdeploy pbds
- In the absence of Dynamic Instrumentation, one could drop/remove a pbd in the hotdeploy folder and have new Instances instrumented.
- Dynamic log changes
- Currently, changing the log level on the .NET Agent requires restarting the applications. Quite painful when trying to debug an issue.
In the "Medium/Large" menu, we have:
- WCF – other bindings
- We already support some WCF bindings, but not all of them, do we need to?
- .NET MVC
- Provide OOTB tracers for Microsoft's .NET MVC framewok key classes
- Spring MVC 5 support
- Same as above for the Spring MVC framework
- Backend HTTP Tracing
- Trace outgoing HTTP calls, similar to APM 10's HTTP Tracing functionality for Java Agents
- .NET Remoting
- Being able to trace and correlate .NET applications and transactions communicating through .NET remoting
- APM Command Center
- Have .NET Agents show up in ACC's Agent list and diagnostic reports
- .NET 4.5 full support
- Support new constructs of the .NET language in .NET 4.5
- WCF – async
- Support for the WCF asynchronous communications
- Memory overhead improvements
- Significantly reduce the memory footprint of the .NET Agent
- Dynamic Instrumentation
- Being able to change the instrumentation level of a class/method at runtime
- Smart Instrumentation
- Collect Deep Transaction Traces automatically, automatically capture Deep Transaction Traces on Errors or Threshold violation, automatically detect entry points, etc...
If you're interested in shaping the future of the .NET Agent, take the .NET Agent future Survey