Backward compatibility for older agents

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

  1. Backward compatibility is not provided for these agents. The client has to upgrade to the latest agent.
  2. 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) : 

  1. Open the apminsight.conf file present in the gem installed folder.
  2. 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.
  3. Change apm.host to contain the URL used to access the AppManager instance. 
  4. Sample configuration : 
license.key=APMI_7444740810313e8fac
apm.host=https://localhost:8443/
  1. Save and close the file.
  2. Restart the Ruby Application being monitored.
  3. The agent should now be compatible with the latest Applications Manager instance.

                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • APM Insight - Agents Troubleshooting and Compatibility Guide

                        To optimize performance and troubleshooting, Please provide the following details related to the respective agents and cross-verify compatibility from the provided help pages. Java Agent Application Server & Version : __________________ [Eg. Apache ...
                      • Verify the authenticity of APM Insight agents with Checksum verification

                        After downloading APM Insight agents, verify the integrity of the downloaded files by validating their checksum. This ensures that the agents are secure and not tampered by any external malicious code or software. After downloading the agent, ...
                      • EUM Agent - Allowing multiple agents with same host name

                        Question: How do I assign multiple agents with same host name? Answer: You have the option to allow multiple agents with same host name under EUM Agent. When should one select this option? This option is provided mainly for a network which has ...
                      • RBM - The Firefox browser does not launch for EUM agents installed on a Linux server

                        Each version of Mozilla Firefox comes with a set of system requirements to ensure the proper functioning of the web browser. For Real Browser Monitoring, we use Mozilla Firefox version 45. The system requirements for Real Browser Monitoring can be ...
                      • APM Insight agent log paths

                        Folder path to view .NET agent logs .NET agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData\ from Vista onwards, which is a hidden folder). Check the following folder paths: For agents v2.5.4 and ...