Add a deleted .NET instance | Site24x7 APM

How to add an instance that was deleted earlier (For .NET and .NET Core agents)

Steps for .NET agent

  1. Navigate to the below paths:
    1. %ProgramData%\DotNetAgent\
    2. %ProgramData%\DotNetCoreAgent\ (For agent version 6.8 and above)
  2. Delete the apminsight.net.info file from the folder with the same name as the application.
    Note: The name of the monitor folder created for the selected application will be the same as that application's name.
  3. Restart the APM Insight .NET Agent service.
    Note: It will recycle the application pools.
  4. Perform some transactions manually.

Steps for .NET Core agent

Notes
The following steps are applicable for .NET Core agent version 6.7 and below. For agent version 6.8 and above, please follow the .NET steps given above.
You can follow any of the below methods.

Adding agent via PowerShell

  1. Navigate to the path: [AgentDestinationPath]\Site24x7DotNetCoreAgent\
  2. Delete the apminsight.net.info file found in the folder with the same name as the application.
    Note: The name of the monitor folder created for the selected application will be the same as that application's name.
  3. Restart the .NET Core applications.
  4. Perform some transactions manually.

Adding agent via NuGet package

  1. Navigate to the application's publish directory.
  2. Navigate to the DotNetAgent\[Application Name] folder.
  3. Delete the apminsight.net.info file.
  4. Restart the .NET Core application.
  5. Perform some transactions manually.

Adding agent via Azure App service extension (For .NET and .NET Core)

  1. Navigate to http://[yoursitename].scm.azurewebsites.net in your web browser.

  2. Go to Debug Console > CMD to open the file explorer.


  3. Navigate to the following path: Site24x7DotNetAgent\DotNetAgent_[servername]\[yourAppName]
    Note: If the path is not available, upgrade the APM Insight extension to the latest version.

  4. Delete the apminsight.net.info file.


  5. Restart the Azure App Service and start performing some transactions manually.

    • Related Articles

    • Bundled .NET and .NET Core agents in a single MSI

      In APM Insight .NET agent version 6.8.0, the .NET and .NET Core agents have been bundled into a single MSI, enabling unified monitoring of both application types. Upgrade requirements for .NET Core agent 6.7 and below If you're using .NET Core agent ...

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

    • How does Site24x7 always ensure the availability of its location agents during monitoring?

      Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...

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

    • Device/Licence Key

      Device Key is a unique and secure alphanumeric key that can be accessed by logging in and navigating to Admin > Developer > Device Key. It is an authentication mechanism where the Site24x7 agent pushes the performance metrics to site24x7.com to ...