Identifying APM conflicts with a health monitor tool

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 installation is complete.
2. The .NET monitor stopped receiving data from the application.
Prerequisite: The Site24x7 APM Insight .NET agent should be installed.

Video



Please follow the steps outlined below to identify and resolve the conflict between the other APM product and the APM Insight.NET agent.

Profilers that commonly conflict with the Site24x7 .NET agent

Environment variable of Site24x7's .NET agent:
{989D151B-3F31-482E-926F-2E95D274BD36}

Other APM profilers
Profiler CLSID
AppDynamics
AppDynamics.AgentProfiler
New Relic
{71DA0A04-7777-4EC6-9643-7D28B46A8A41}
Dynatrace
{DA7CFC47-3E35-4c-4e-B495-534F93B28683}

{B7038F67-52FC-4DA2-AB02-969B3C1EDA03}
IntelliTrace
{2AA1AA98-2CAA-4FCF-86CE-EFA007737E83}
Microsoft Application Insights
{324F817A-7420-4E6D-B3C1-143FBED6D855}
SCOM APM
{AD5651A8-B5C8-46ca-A11B-E82AEC2B8E78}
JetBrains dotCover
{9AA5D52F-37E2-487D-AAEC-727478B8BDB5}

Identify the conflict using the .NET Health Monitor

  1. Open the .NET Health Monitor by navigating to Start > All Programs > APM Insight .NET Agent > APM Insight .NET Agent Health Monitor.
  2. If any other APM products conflict with the APM Insight .NET agent, you will be notified, as shown in the image.

You can now use the Process Explorer or the Event Viewer to identify which product conflicts with the APM Insight .NET Agent.

Identify the conflicting APM product using Process Explorer

  1. Install and open the Process Explorer.
  2. Select w3wp.exe, go to the Environment tab, and look for the COR_PROFILER variable to identify the conflicting APM product.
Please find the link to download and install the Process Explorer in your system.


Identify the conflicting APM product using Event Viewer

  1. Open Event Viewer and navigate to Windows Logs > Application.
  2. Click the event with the source .NET Runtime to check the Profiler CLSID of the conflicting APM product.
The Event Viewer will be installed on your Windows machine by default.


Resolve the conflict

  1. You must uninstall the other APM product because Microsoft restricts using multiple profilers on the same machine.
  2. Perform IIS reset.
  3. Now, you can restart your application and make some transactions.
  4. Once the application is up and receiving requests, you can view the monitor under APM > APM Insight > Applications in the Site24x7 client.
  5. If you click the application name, you can also view the metrics and the corresponding graphs.


    • Related Articles

    • Identify and correct hostname mismatches while cloning

      Use the health monitor to correct host name mismatches, when cloning from a server in which the APM Insight .NET agent has been installed. Open the Health Monitor tool as follows: Start > All programs > APM Insight .NET Agent > APM Insight .NET Agent ...

    • How to add APM Insight Java agent without application restart?

      In general, after installing the APM Insight Java agent, you have to restart your application for the agent to capture monitoring data. But in case of critical issues in the app, like sudden application slowness, where you haven't installed APM ...

    • DC migration steps for APM Insight agents

      For Server based installations 1. Obtain the new device key. 2. Update the license.key value in the APM Insight configuration file (or the environment variable mentioned) with the new device key. The location varies for each agent, as listed below: ...

    • DC migration steps for APM Insight Node.js agent

      Obtain the new device key. Update the licenseKey value in the apminsighnode.json file located at the <application root directory>. Log in to the server and delete the existing instance information file apminsight.json located at <application root ...

    • DC migration steps for APM Insight Ruby agent

      Obtain the new device key. Update the license.key value in the apminsight.conf file located at <APP_HOME>/. Log in to the server and delete the existing instance information file, apminsight.info, located at <APP_HOME>/. Restart the Ruby application. ...