Configure Application Filters for .NET Core applications

You can exclude select .NET Core applications from being monitored by APM Insight. This will help exclude unwanted applications and result in efficient use of your license. As practising Dot NET Core monitoring is essential for the smooth running of .NET Core applications, you can use the following steps to monitor select .NET Core applications using APM Insight.

• .NET core agent v6.0 and above
• .NET Core agent v5.4 and below

Note: This is applicable only for applications hosted in IIS.

.NET core agent v6.0 and above

Follow the steps below to monitor specific .NET Core applications:

1. Filter .NET Core applications hosted on IIS
2. Filter .NET Core applications running as standalone processes or Windows services
3. Filter .NET Core applications running as Windows services

1. Filtering .NET Core applications hosted on IIS

1. Navigate to the folder where the .NET Core agent is installed.
2. Open the appfilter.config file in the text editor.
3. Add or modify the app pool name and its corresponding monitor name as shown below:

   <?xml version="1.0" encoding="utf-8" ?>
   <applications>
   <application AppPoolName="<Your_Application_Pool_Name1>"MonitorName="<Your_APM_Application_Name1>" />
   <application AppPoolName="<Your_Application_Pool_Name2>"MonitorName="<Your_APM_Application_Name2>" />
   <application AppPoolName="<Your_Application_Pool_Name3>"MonitorName="<Your_APM_Application_Name3>" />
   </applications>

   Note: Since applications in the .NET Core agent are monitored or excluded based on their application pool name, it is important to specify the name of the corresponding application pool. You can also use the same name or a new name to monitor the IIS applications in Applications Manager.

4. Save the appfilter.config file.
5. Recycle the application pool or use the IISRESET command to restart it.
6. Perform transactions in the application to view data in the Applications Manager console.

2. Filtering .NET Core applications running as standalone processes or Windows services

1. Navigate to the folder where the .NET Core agent is installed.
2. Open the netcore_appfilter.config file in the text editor.

Note: For .NET Core agent versions upto v6.0.2, the applications running as Windows services can be filtered by executing netcore_appfilter.config file.

3. Add or modify the process name and its corresponding monitor name as shown below:

   <?xml version="1.0" encoding="utf-8" ?>
   <processes>
   <process Name="<Your_ApplicationProcess_Or_WindowsServiceProcess_Name1>.exe"MonitorName="<Your_APM_Application_Name1>" />
   <process Name="<Your_ApplicationProcess_Or_WindowsServiceProcess_Name2>.exe"MonitorName="<Your_APM_Application_Name2>" />
   <process Name="<Your_ApplicationProcess_Or_WindowsServiceProcess_Name3>.exe"MonitorName="<Your_APM_Application_Name3>" />
   </processes>

   Note: You can set the same name or a new name to monitor the application in Applications Manager.

4. Save the netcore_appfilter.config file.
5. Restart the standalone .NET Core application or the .NET Core Windows service to create the monitor.
6. Add the application methods to the custom instrumentation to collect performance metrics, as shown in the following steps:
   1. Log in to Applications Manager.
   2. Navigate to APM tab → Your application → Monitor Actions → Edit, which directs you to the Edit APM Insight Application Configuration window.
   3. In the Custom instrumentation field, add the class method that is called periodically in the Windows service or the method that is triggered most of the time in a standalone application.

      

   4. After specifying the required class method, save the configuration and wait for a couple of minutes.
   5. Now restart the .NET Core application to start monitoring.

3. Filtering .NET Core applications running as Windows services

Note: The option to filter .NET Core applications running as Windows services is applicable only for .NET Core agent versions from 6.3.0

1. Navigate to the folder where the .NET Core agent is installed.
2. Open the windowsservice_appfilter.config file in the text editor.
3. Add or modify the app pool name and its corresponding monitor name as shown below:

   <?xml version="1.0" encoding="utf-8" ?>
   <windowsServices>
   <windowsService ServiceName="<Your_Windows_service_Name1>" MonitorName="<Your_APM_Application_Name1>" />
   <windowsService ServiceName="<Your_Windows_service_Name2>" MonitorName="<Your_APM_Application_Name2>" />
   <windowsService ServiceName="<Your_Windows_service_Name3>" MonitorName="<Your_APM_Application_Name3>" />
   </windowsServices>
   

   Note: You can either set the same name as the Windows service or choose a different name for the applications's monitor.

4. Save the windowsservice_appfilter.config file.
5. Restart the configured .NET Core Windows services to start monitoring.

.NET Core agent v5.4 and below

Follow the steps given below to configure application filters for .NET Core agent v5.4 and below:

1. Navigate to the .NET Core agent folder.
2. Open the appfilter.config file in the text editor.
3. Add or modify the app pool name and its corresponding monitor name as shown below.

   <?xml version="1.0" encoding="utf-8" ?>
   <applications>
   <application AppPoolName="<Your_Application_Pool_Name1>" MonitorName="<Your_APM_Application_Name1>" />
   <application AppPoolName="<Your_Application_Pool_Name2>" MonitorName="<Your_APM_Application_Name2>" />
   <application AppPoolName="<Your_Application_Pool_Name3>" MonitorName="<Your_APM_Application_Name3>" />
   </applications>

   Note: Unlike .NET agent, applications are monitored or excluded based on their application pool name in .NET Core agent. This is why you need to enter the corresponding application pool name. You can also set the same name or a new name by which you want to monitor the app pools in Applications Manager.

4. Save the appfilter.config file.
5. Recycle the application pool or run the RESET IIS command.
6. Perform transactions in the application to view data in the Applications Manager console.