Related pages: |
The AppDynamics .NET Agent includes an embedded .NET Machine Agent that runs as part of the AppDynamics.Agent.Coordinator
service. Among other things, the Machine Agent regularly gathers system performance data and reports it back to the Controller as metrics.
Note: Because the .NET Agent includes an embedded .NET Machine Agent, it consumes a Machine Agent license. Meaning that installing .NET Agent, consumes both one APM license, and one Machine Agent license.
Do not confuse the .NET Machine Agent with the Machine Agent, a Java application. The Machine Agent provides the capability to use extensions such as plugins, metric listeners, and orchestrations. See Machine Agent. |
The app agent MSI file and .NET Agent Configuration Utility automatically install and configure the .NET Machine Agent to connect to the Controller. The connection information is the same for the app agent and the .NET Machine agent. See Configure the .NET Agent.
To manage the .NET Machine Agent from the Controller, see 'Manage the .NET Machine Agent' on Monitor Windows Hardware Resources.
Customize instrumentation settings for the Machine Agent element in the config.xml file. See 'Where to Configure Agent Properties' on Administer the .NET Agent.
Edit the config.xml
file as an administrator. See 'Where to Configure Agent Properties' on Administer the .NET Agent.
Modify the machine-agent
element and add any children elements according to the .NET Machine Agent configuration topics.
Save the config.xml
file.
AppDynamics.Agent.Coordinator
service.These topics describe specific customizations for the .NET Machine Agent:
If you want to monitor the Windows hardware performance data, but do not want to monitor any .NET applications, you can configure the .NET Machine agent to run without the .NET Agent.
config.xml
file.