How can I configure application filtering for the .NET Agent on non-desktop Windows servers?
Steps to follow
Non-Windows desktop servers have the capability to set up application filtering for monitoring exclusively through the agent configuration file. To configure application filtering for your non-Windows server, follow the steps given below:
- Open the specified Configuration file using a text editor.
- Locate the Application filtering settings.
- Modify the application settings to your requirements.
- Save the changes made to the configuration files.
- Restart the agent to apply the new settings.
IIS Sites Filtering
Configuration File: C:\ProgramData\DotNetAgent\appfilter.conf
Description: Specify the IIS Sites and their corresponding APM names for monitoring. If APM names are not needed, leave the value field empty.
- To Enable Application Filtering: Specify whether the applications are to be filtered. Default value: TRUE.
use.app.filters=True
- To List IIS Sites: Specify which applications are to be monitored. The values should be provided as a JSON-formatted string, and the input is case-insensitive.
For Example:
Window Service App Filtering
Configuration File: C:\ProgramData\DotNetAgent\windows_appfilter.conf
Description: List the Windows services and their corresponding APM names for monitoring. If APM names are not needed, leave the value field empty.
- To Enable Windows Service Monitoring: Specify whether the Windows services are to be monitored or not. Default value: FALSE
enable.windows.services=True
- To List Windows Services: If the Windows service option is enabled, include the specified services for monitoring. Please use a JSON-formatted string; it is case-insensitive. Use the executable file name as the key and the service display name as the value.
For Example:include.service.names={"com.docker.service_com.docker.service_1.0.0.0":"Docker Desktop Service"}
Window Desktop App Filtering
Configuration File: C:\ProgramData\DotNetAgent\standalone_appfilter.conf
Description: List the Windows Desktop applications and their corresponding APM names for monitoring. If APM names are not needed, leave the value field empty.
- To List Windows Desktop Apps (XML format): The application specified in this field will be included for monitoring. Please use XML formatting, and it is case-insensitive. The key will be executable file name, and the value will be app display name.
For Example:<applications><application executable="docker desktop.exe_4.3.2.72729" name="Docker Desktop" /></applications>
New to ADSelfService Plus?
Related Articles
How .NET agent collects data?
APM Insight .NET Agent is a profiling based monitoring solution. It uses the profiling APIs provided by Microsoft frameworks and hooks itself into the ASP.NET worker process. The general workflow for monitoring is as given below : The .NET agent ...Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...APM Insight agent log paths
Folder path to view .NET agent logs .NET agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData\ from Vista onwards, which is a hidden folder). Check the following folder paths: For agents v2.5.4 and ...How do I verify that the agent is actually hooked onto the application process?
1. Ensure your application (IIS app, Windows service, desktop app) is enabled for monitoring within the "APM Insight .NET Agent Configuration" tool and your application is running & processing transactions or requests for the agent to monitor it. 2. ...