Backward compatibility for older agents
Java Agent (v2.3 and below) :
- Open the apminsight.conf file present in the agent installation folder.
- Add an extra entry 'license.key'. The value for this would be the license key shown in the help card present in the home page of the APM Insight tab in the AppManager Instance.
- Change apm.host to contain the URL used to access the AppManager instance.
- Sample configuration :
license.key=APMI_7444744496936081031ac
apm.host=http://localhost:9090/
- Save and close the file.
- Restart the Java Application being monitored.
- The agent should now be compatible with the latest Applications Manager instance.
DotNet Agent (v2.5.4 and below) :
- Backward compatibility is not provided for these agents. The client has to upgrade to the latest agent.
- While configuring the new agent, if the client provides the same application name as the existing instance, the monitor will be reused.
Ruby Agent (v1.1. and below) :
- Open the apminsight.conf file present in the gem installed folder.
- Add an extra entry 'license.key'. The value for this would be the license key shown in the help card present in the home page of the APM Insight tab in the AppManager Instance.
- Change apm.host to contain the URL used to access the AppManager instance.
- Sample configuration :
- Save and close the file.
- Restart the Ruby Application being monitored.
- The agent should now be compatible with the latest Applications Manager instance.
New to ADSelfService Plus?