Data collection in .NET agent

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 monitoring starts when the profiler is loaded into the respective application's worker process (w3wp.exe)
    • A worker process is initialized and/or an app domain is created for an application on the first request it processes. So no data collection will happen if no request is processed by the application
    • In the current version of the agent, the profiler can only be loaded/unloaded during process start/stop. This is the reason for recycling app pools (prior to version 2.5, an iisreset was done) when there is a change in appfilter configurations
  •  When monitoring begins, a seperate thread is spawned in the application which establishes connection with the Windows service and sends monitoring data as and when it happens   
    • Monitoring data is collected inside each of the request threads and is sent to the Windows service
    • If the web application is idle or there are no incoming requests, no data will be sent to the service
  • The Windows service aggregates data from each application and sends it to the Site24x7 servers once every minute
    • If there is no data for a particular application, empty data is sent, so that status of the application in Site24x7 console is UP
    • Related Articles

    • Site24x7 Real User Monitoring (RUM) - Data Collection

      When you include Site24x7 RUM beacon script in your web pages, the following data is collected. All data that's being collected is in accordance with GDPR compliance.  Performance details of web page load time - Metrics like response time of web page ...
    • How to enable or disable application filters in the .NET Core agent?

      The APM Insight .NET Core agent is designed to monitor IIS-hosted applications based on the list entered in the appfilter.config file in the agent's installation location. Irrespective of the filter, we can monitor all .NET Core applications hosted ...
    • Troubleshooting steps when there is an exception while monitoring ASP .NET applications.

      Use Case: Sometimes, you may receive the exception "Loading this assembly would produce a different grant set from other instances.", while running the APM Insight .NET agent in your ASP .NET applications. This is because, by design, the agent works ...
    • APM Insight agent log paths

      Folder path to view One agent logs One agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData from Vista onwards). Check the following folder path in Windows: C:\ProgramData\Site24x7APMOneAgent\Logs ...
    • How to verify the license key for a .NET application

      Problem Statement: The APM Insight .NET monitor is not created in the Site24x7 web client because of an empty or invalid license key. Prerequisite: The Site24x7 APM Insight .NET agent should be installed. Steps to verify the license key Navigate to ...