After you install the Application Real-Time Monitoring Service (ARMS) agent, the host IP address in the monitoring console may be missing or incorrect. This happens when the host has multiple network interface controllers (NICs), and the agent picks up an IP address from the wrong interface.
Diagnose the issue
Log on to the host where the ARMS agent is installed and run the following command to list all network interfaces:
ifconfig -aIf the output shows multiple NICs, the ARMS agent likely selected the IP address from the wrong interface.
Specify the correct IP address or NIC
Add one of the following JVM parameters to your application startup configuration.
Option 1: Specify an IP address
Add the -DEAGLEEYE.LOCAL.IP parameter to set the IP address that the ARMS agent reports:
-DEAGLEEYE.LOCAL.IP=[$IP]| Parameter | Description | Example |
|---|---|---|
[$IP] | The IP address to use for data collection. Use the IP address of the NIC that connects to your monitoring network. | 192.168.1.100 |
Option 2: Specify a NIC
Add the -DNETWORK.INTERFACE parameter to bind the ARMS agent to a specific NIC:
-DNETWORK.INTERFACE=[$Network_Card]| Parameter | Description | Example |
|---|---|---|
[$Network_Card] | The name of the NIC to bind the agent to. | eth0, bond0 |
Example: Apache Tomcat
To apply either parameter in Apache Tomcat, add it to the JAVA_OPTS variable in {TOMCAT_HOME}/bin/catalina.sh:
JAVA_OPTS="$JAVA_OPTS -DEAGLEEYE.LOCAL.IP=[$IP]"Or:
JAVA_OPTS="$JAVA_OPTS -DNETWORK.INTERFACE=[$Network_Card]"After you modify catalina.sh, restart Tomcat for the change to take effect.
Verify the result
After the application restarts, check the ARMS console to confirm that the correct IP address is displayed for the host.