Configure Application Filters for .NET Core applications

You can exclude selected .NET Core applications from being monitored by Site24x7 APM Insight. This will help in the exclusion of unwanted applications and result in the most efficient use of your license.

Follow the steps below to monitor selected .NET Core applications with Site24x7 APM Insight.

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

Next step: You can also configure custom instrumentation to get more trace details.

1. Steps to filter .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.
   
   
   copied

   <?xml version="1.0" encoding="utf-8" ?>
   <applications>
   <application AppPoolName="Your_Application_Pool_Name"
   MonitorName="Your_APM_Application_Name" />
   </applications>

   Note

   Unlike in the .NET agent, applications in the .NET Core agent are monitored or excluded based on their application pool name. This is why you must enter the name of the corresponding application pool. You can also use the same name or a new name to monitor the IIS applications in Site24x7.

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 Site24x7 console.

2. Steps to filter .NET Core applications running as standalone processes

1. Navigate to the folder where the .NET Core agent is installed.
2. Open the netcore_appfilter.config file in the text editor.
3. Add or modify the process name and its corresponding monitor name, as shown below.
   
   
   copied

   <?xml version="1.0" encoding="utf-8" ?>
   <processes>
   <process Name="Your_ApplicationProcess_Name.exe"
   MonitorName="Your_APM_Application_Name" />
   </processes>

4. Save the netcore_appfilter.config file.
5. Restart the standalone .NET Core application to create the monitor.

3. Steps to filter .NET Core applications running as Windows services

1. Navigate to the folder where the .NET Core agent is installed.
2. Open the \Site24x7DotNetCoreAgent\DotNetAgent\windowsservice_appfilter.config file in a text editor.
3. You can add or modify the Windows service name and its corresponding monitor name, as shown below.
   
   
   copied

   <?xml version="1.0" encoding="utf-8" ?>
   <windowsServices>
       <windowsService ServiceName="Your_Windows_Service_Name" MonitorName="Your_APM_Application_Name" />
   </windowsServices>

   Note

   You can either provide the same name as the Windows service or choose a different name for the application's monitor.

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

Configure custom instrumentation to get more trace details

By default, the agent instruments application framework methods. You can customize the instrumentation by configuring your application methods to get more trace information.

Add the application methods to the custom instrumentation to collect performance metrics, as shown in the following steps.

1. Log in to Site24x7. 
2. Navigate to APM Insight and select your .NET Core application monitor.
3. Hover over the hamburger menu icon (≡) and select Edit, which directs you to the Edit APM Insight Application page.
4. 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.
   
   Syntax:
   
   
   
   Example:
   
   
   
   
5. Save the configuration and wait for a couple of minutes.
6. Now restart the .NET Core application to start monitoring.