The .NET Agent monitors Microsoft Common Language Runtimes. It is loaded by a CLR and configured through global environment variables and enabled for individual processes using the .NET Agent configuration tool. So, this agent is always loaded but only active when enabled for a specific process.
Please see .NET Agent configuration to learn how to configure the Agent.
|GUI controls||.NET Windows Forms|
|.NET AMQP Receive Entry Point|
|MSMQ Receive Entry Point|
|.NET Service Fabric|
|Test framework||.NET Test|
|Threads||.NET Thread Tagging|
|.NET Web Request|
|Web Service||.NET Web Service Tagging|
OneAgent released as BETA functionality for AppMon 2017 May. Please be aware that:
- Not all features/sensors available in Classic Agent are already available in the OneAgent for AppMon
- Features/Sensors known from Classic Agent can behave differently
To use OneAgent in AppMon 2017 May you need to install Classic Agents first, and then roll them out to the OneAgent. No additional configuration needed. Before you switch to OneAgent, double check your major requirements with the available feature set.
You must not use the OneAgent in your production environment. The aim of BETA is to test it in pre-production environment, and see how the new Agent affects your custom dashboards/configurations you use to monitor your production environment.
.NET Core requires OneAgent.
It is recommended to use OneAgent for following scenarios:
- To monitor Microsoft Azure
- To improve Collector scalability
- To resolve Collector connectivity problems
- To reduce AutoSensor overhead.
|Custom Perfcounter metrics|
|Deep object access|