Add APM Insight application name as JVM argument

Mention APM Insight application name as a JVM argument

To mention APM Insight application name in JVM parameters, kindly add the following line to the arguments

      -Dapminsight.application.name=your_app_name

This will override the value specified in apminsight.conf file.

Example:
In Windows, set JAVA_OPTS=%JAVA_OPTS% -Dapminsight.application.name=MyApplication
In Linux, export JAVA_OPTS="$JAVA_OPTS -Dapminsight.application.name=MyApplication"

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

    • How to add APM Insight Java agent without application restart?

      In general, after installing the APM Insight Java agent, you have to restart your application for the agent to capture monitoring data. But in case of critical issues in the app, like sudden application slowness, where you haven't installed APM ...

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

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

    • DC migration steps for APM Insight Python agent

      Obtain the new device key. Update the license.key value in the apminsight_info.json file located at the <application root directory>. Log in to the server and delete the existing instance information file located at the <application root ...