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 path: %ProgramData%\DotNetAgent\
  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 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

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

    • How to add a PHP instance that was deleted earlier

      For agent versions 4.0 and above For every instance, there will be a corresponding configuration file present inside the conf folder of the S247DataExporter installation path. Delete the appropriate configuration file and restart the S247DataExporter ...

    • DC migration steps for APM Insight .NET and .NET Core agents

      .NET agent Obtain the new device key. Log in to the server and update the license.key value in the apminsight.conf file located at %ProgramData%\DotnetAgent\<appname>. Delete the existing instance information file, apminsight.net.info, located at ...

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

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

    • Understanding log upload add-ons for large, medium, and small storage needs

      For customers who purchase logs after August 2024, the default log search retention is set to seven days. In this doc, we will cover: For 10GB log upload requirement For 1TB log upload requirement For 500GB log upload requirement For 100GB log upload ...