Understanding automatic integration of Site24x7 APM and server monitors
Server and APM instance integration happens automatically in the Site24x7 console. Once integrated, the performance metrics of the integrated servers are displayed in the
Server Metrics tab on the APM details page.
- During APM instance monitor creation, if a server monitor already exists for this host, it will be automatically integrated with the APM instance monitor.
- During APM instance monitor creation, if a server monitor does not exist for this host, install a new server monitor on the host and restart the APM instance monitor for the integration to happen.
The APM instance monitor and the server monitor must have the same hostname or domain name.
Related Articles
How to rename an APM Insight application?
Site24x7 APM Insight doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the apminsight.conf file and the agent associated with that instance will ...
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 Java agent
Obtain the new device key. Update the license.key value in the apminsight.conf file located at <apminsight-javaagent.zip Extracted Directory>/. Log in to the server and delete the existing instance information file apminsight.info located at ...
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. ...