Troubleshooting steps for APM insight monitors

Troubleshooting steps when the monitor is not getting added after buying advance monitor add-on

  • Delete the apminsight.info file found under the below path - %ProgramData%\DotNetAgent\[Application name] 
  • Note: The [Application name] will be the name of the monitor folder created for selected application
  • Restart the APM Insight .NET Agent service
  • Perform some transactions manually

    • Related Articles

    • Unable to add SQL insight monitor

      If the SQL Insight monitor is not getting added even after entering your credentials, try these troubleshooting steps: Ensure that the Auto-discover applications feature is enabled. If not, you will need to trigger discovery using the Discover ...

    • Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers

      Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...

    • Basic troubleshooting tips for the APM Insight Node.js agent

      If you are experiencing issues after installing the APM Insight Node.js agent, follow these troubleshooting tips. Verify agent installation and connectivity To verify the agent installation status, you can execute the following command from the root ...

    • How can I choose resources in a monitor group for third-party integration

      By associating the monitor group with a tag, you can select the resources in a monitor group for third-party integration. Read how to add a tag to a monitor group.    Once you have added a tag to the group, choose the tag to integrate the resources ...

    • Troubleshooting steps when no data is received from the SQL server

      As we use "Perfmon" to fetch data for Microsoft SQL monitoring, please check if the counters related to SQL are present in the user's perfmon. Please follow the steps below: Open the server machine in which the issue is occurring. Start -> Run and ...