Steps for APM Insight agents to migrate to a new DC

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:

 Agent type
 File name
 File location (Relative or Absolute)
 JAVA
 apminsight.conf
 <apminsight-javaagent.zip Extracted Directory>/
 RUBY
 apminsight.conf
 <APP_HOME>/ 
 DOTNET
 apminsight.conf
 %ProgramData%\DotnetAgent\<appname>
 DOTNET_CORE
 apminsight.conf
 <ApplicationPublishDirectory>\DotnetAgent\
 PHP_WINDOWS
 apminsight.conf
 <INSTALLPATH>\APM Insight PHP Agent\zpa\bin
 PHP
 apminsight.conf
 /opt/zpa/bin/
 NODEJS
 apminsighnode.json
 <application root directory> 
 PYTHON
 apminsight_info.json
 <application root directory> 
 All (except PHP)
 S247_LICENSE_KEY
 System Environment variable
 DOTNET_CORE (Windows)
 S247_LICENSE_KEY
 Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC 

 Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WAS

3. Log in to the server and delete the existing instance information files. Please find the below for the location of the instance files based on the agent:

 Agent type
 File name
 File location (Relative or Absolute)
 JAVA
 apminsight.info
 <apminsight-javaagent.zip Extracted Directory>/
 RUBY
 apminsight.info
 <APP_HOME>/ 
 DOTNET
 apminsight.net.info
 %ProgramData%\DotnetAgent\<Appname>
 DOTNET_CORE
 apminsight.net.info
 <ApplicationPublishDirectory>\DotnetAgent\
 PHP_WINDOWS
 instance.out
 <INSTALLPATH>\APM Insight PHP Agent\zpa\bin
 PHP
 instance.out
 /opt/zpa/bin/
 NODEJS
 apminsight.json
 <application root directory>/apminsightdata

4. Restart the application server and the respective service. The service name varies for each agent, as listed below:

 Agent type
 Service name
 JAVA
 <application server>  

 (eg: Tomcat, JBoss, etc.) 
 RUBY
 <application> 
 DOTNET
 APM Insight .NET Agent Service (Windows)
 DOTNET_CORE
 <application server> or dotnet process
 PHP_WINDOWS
 APM Insight PHP Agent service
 PHP
 zpdpsvc
 NODEJS
 <application server> or npm process
PYTHON
 <application> 

In Serverless Set-up

In Containers and Kubernetes

  1. Rebuild the image in Environment variables or the apminsight.conf file with the new device key.  
  2. ​Delete the existing information files (if found) under volume mapping.
  3. Stop the existing containers and spawn new ones with the updated image. 

In Elastic Beanstalk

  1. Device key set in .ebextension file
    1. Update the device key present in the .ebextension or apminsight.config file.
    2. Add a command to delete the existing instance information files (refer to above for locations).
    3. Re-deploy the application with the new .ebextension or apminsight.config file. 
  1. Device key set in EBS environment variable
    1. Update the EBS device key from the EBS console by editing the S247_LICENSE_KEY variable.
    2. Add a command to the .ebextension or apminsight.config file to delete existing instance information files (refer to above for locations).
    3. Re-deploy the application with the new .ebextension or apminsight.config file. 

In Azure VM Extension or App Service Extension (.NET & .NET Core)

  1. Uninstall the existing extension.
  2. Reinstall the extension with the updated device key.

Azure Web Apps (Java)

  1. Navigate to the agent extracted directory, usually located in APP_HOME/WEB-INF/lib/site24x7.
  2. Update the device key present in the apminsight.config file.
  3. Delete the apminsight.info file present in the same directory.
  4. Restart the Azure Web App. 

Kubernetes postStart lifecycle (PHP)

  1. Change the apikey parameter for the installation script in the Kubernetes postStart lifecycle event or the values.yaml file in Helm charts.
  2. Re-deploy your application/service. 


    • Related Articles

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

    • APM Insight integration for Next.js in Kubernetes

      To integrate the Site24x7 APM Insight Next.js agent into your Kubernetes application using initContainers with the prebuilt agent image, follow the steps below: Prerequisites A Next.js application container image The Site24x7 APM Insight license key ...

    • Steps to troubleshoot if you see "NO Data" in the Node VM tab

      Problem statement: You are getting No Data under the garbage collection and event loop graphs such as GC Pause Time, GC Pause Frequency, and Event Loop Ticks Per Minute. Prerequisite: The Node.js agent version should be 3.0.0 or higher. Solution: The ...

    • 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 calculate Mobile APM screen load times

      Mobile APM provides load time metrics to help you understand how long it takes for your mobile app screens to load. These load times are calculated by capturing start and end timestamps during specific lifecycle callbacks. Load times for native ...