Connecting Cloud APM agents to Monitoring server
To connect Cloud APM agents to Monitoring server, you must first locally apply an agent patch to update the agent framework and then configure the agent for server connection.
Before you begin
Download the agent patch from IBM Fix Central . Different patches are provided for the following operating systems:
- Linux for System p:
- Linux for System x:
- Linux for System z®:
- Windows (32-bit):
- Windows (64-bit):
- Diagnostics and transaction tracking data are not yet supported by Monitoring. If the V8 agents have been enabled for diagnostics and/or transaction tracking data collection, reconfigure the V8 agents to disable them before you connect the V8 agents to the Monitoring server.
About this task
Diagnostics and transaction tracking data are not yet supported by Monitoring. If the V8 agents have been enabled for diagnostics and/or transaction tracking data collection, they will be disabled during the following procedure.
- Extract the agent patch to the local system where the V8 agent is installed.
From the extracted directory, run the following command to apply the patch:
Note: If the Cloud APM agents to be connected are not installed in the default directory(
/opt/ibm/apm/agenton Linux and AIX®,
C:\IBM\APMon Windows), you must add the installation path install_dir to the command:
The patch will be applied for IBM Monitoring Shared Libraries and IBM GSKit Security Interface.
If the V8 agents have been enabled for diagnostics and/or transaction tracking data collection, reconfigure the V8 agents to disable them.
For more information about how to reconfigure the V8 agent, see the IBM Cloud APM Documentation.
Download the agent configuration pack from the IBM Cloud Pak console. The downloaded package contains agent configuration files for server connection.
- Log in to the IBM Cloud Pak console and click Get Started.
- Go to Administer > Monitoring > Integrations > New integration on the IBM Cloud Pak console.
- In the Standard monitoring agents section, go to the APM V8 Agents tile and click Configure.
- Click Download file to download the
.tarfile to the system where the V8 agents are installed. In the extracted directory, the
.tarfile is for the Linux and UNIX systems, while the
.zipis for all Windows systems. Use the appropriate file in the following steps according to your operating system.
To configure the V8 agent for a Monitoring server connection, extract the
.tarand run the
post\_configscript with the -i and -e options as the user who installed the V8 agent. Use the -i option to specify the agent installation directory and use the -e option to specify the path to the
env.propertiesfile in the extracted directory.
./post_config.sh -i agent_install_dir -e env.properties
post_config.bat -i agent_install_dir -e env.properties
where agent_install_dir is the V8 agent installation directory.
(WebSphere® Applications agent only) If the V8 agent has been enabled for diagnostics and/or transaction tracking data collection, they have been disabled now. Restart the application server for the data collector to update the configuration.
All V8 agents installed on the same system are configured to connect to the Monitoring server. However, you can view monitoring data only for the supported agents on the IBM Cloud Pak console.
What to do next
- Open the IBM Cloud Pak console to view monitoring data for the supported agents.
- If you are sure that you no longer need to reconnect the agents to the Cloud APM server, remove the offline agents from the Cloud APM console. For more information, see the Viewing and removing offline agents topic in the IBM Cloud APM Documentation.
- To reconnect the agents to the Cloud APM server, see Reconnecting Cloud APM agents to Cloud APM server.