The .NET Agent automatically instruments IIS applications only. However, you can have Windows services or standalone .NET applications instrumented by manually configuring the .NET Agent, as described here.
To instrument Windows services and standalone .NET applications, you configure the applications manually in the .NET Agent configuration file, config.xml.
Before starting, you should verify that the services or applications to be instrumented are actually .NET applications rather than native applications or another type of application. From a command line, run the following command:
The output lists the processes that have DLLs starting with mscor*, indicative of .NET processes. Processes that are not on the list are not .NET processes and cannot be instrumented with the .NET Agent.
If you have previously instrumented IIS applications on the server that hosts the Windows services and standalone applications, the server should already have a config.xml file that you can edit. If not, perform the following steps to generate one:
- Install the .NET Agent. See Install the .NET Agent for more information.
- Run the AppDynamics Agent Configuration utility, as described in Configure the .NET Agent.
If you want to avoid instrumenting IIS applications on the server while running the utility, choose the manual tier naming approach and then simply omit the step of assigning tiers for the IIS application. This disables instrumentation for the IIS applications, allowing you to instrument only the intended Windows services or standalone applications.
The utility performs these configuration tasks:
- Changes the location of the logs directory and assign permissions.
- Configures and tests connectivity to the Controller.
Sets the business application for the agent.
Manually Configure the .NET Agent
Once you have configured the Controller properties for the .NET Agent, instrument your Windows service or standalone application by adding the Standalone Applications element to the config.xml.
Edit the config.xml file as an administrator. See Administer the .NET Agent.
If you haven't instrumented any IIS applications, the file contains the minimal configuration for the Controller connectivity and the machine agent. Verify the Controller properties and the Business Application name, as in the following example:
If you have already instrumented IIS applications, those configurations appear under the IIS element.
Add a single standalone applications element (
standalone-applications) under the app-agents element, and under the
standalone-applicationselement, add a standalone application element (
standalone-application) for each Windows service or standalone application to instrument. For example:
In the standalone application element configuration:
tierelement to assign the instrumented application to a tier in the Controller. See .NET Agent Configuration Properties.
Identify the application's executable file in the Standalone Application element
executableattribute using one of the following formats:
Executable name. For example, MyStandaloneApp.exe or MyWindowsService.exe. The file extension is optional, so MyStandaloneApp also works.
- Full or partial path to the executable. For example, C:\Program Files\MyApplication\MyStandaloneApp.exe or MyApplication\MyStandaloneApp.exe. Use the full or partial path when you want to assign different AppDynamics tiers to separate instances of the same executable file running from different paths.
To differentiate between two instances of the same executable, specify any unique portion of the application's command line invocation format, such as an argument, in the Standalone Application command-line attribute.
You can discover the path to a Windows service executable in the Services panel of the administrative tools. In Services, click on the service and choose Properties. The path appears in the General tab.
Restart the AppDynamics.Agent.Coordinator service.
Restart the Windows service or standalone application.
If your Windows service or standalone application doesn't implement an auto-detected framework, you must configure a POCO entry point for a class/method in your service for the agent to begin instrumentation.
Sample Configuration File
This sample config.xml demonstrates instrumentation for a Windows service and standalone application: