Steps to be performed when an application is not getting added by the .NET agent profiler in APM

• Related Articles

• Unable to see application after adding APM Insight .NET agent and getting "Failed to Load Profiler" error

  The following are few reasons that might pose an interference with the APM Insight .NET agent profiling: 1. User Permission settings 2. Competing profilers/monitoring services If the installation is not done with administrative privileges, the ...

• APM Insight monitor not getting added to my account

  The most probable reason will be a wrong license key used while adding the agent. Check if you have added the agent in the application with the correct license key. If you have used the correct license key and still the monitor is not getting added, ...

• How to configure VirSec RASP APM profiler and Site24x7 .NET agent on the same machine

  You can install both the Site24x7 APM Insight .NET Agent and VirSec RASP profiler on the same machine to monitor your .NET and .NET Core applications. Steps to configure the .NET agent with VirSec By default, both and Site24x7 use the same ...

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

• How to identify and resolve conflicts between other APM products and the APM Insight .NET agent

  Problem statement: You are experiencing either of the below issues and suspect that another APM product is interfering with the Site24x7 .NET agent. 1. The .NET monitor is not created under APM > APM Insight > Applications, even after the .NET agent ...