Limitations of Custom instrumentation in .NET agent

Limitations of custom instrumentation in .NET agent

While most of the functions can be instrumented using custom instrumentation, the following kinds of methods will be ignored for profiling:

1. Constructors
2. Object finalizers and Disposer methods
3. Lambda functions
4. Property getter / setter 

    • Related Articles

    • FAQs related to Windows Service monitoring

      After installing APM Insight Windows service monitoring agent , if you don't see data in the Site24x7 console, or if you are unable to add monitors, kindly follow the below given steps to troubleshoot. If few monitors are not getting added: Check for ...

    • 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 ...

    • 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 ...

    • 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 ...