Installing agents
You can install any combination of monitoring agents on a managed system. For example, if you install the Ruby agent to monitor Ruby On Rails applications, you might want to also install the Response Time Monitoring Agent, the Linux® OS agent, or both agents. With the Response Time Monitoring agent, you can gather more response time information for your Ruby applications. With the Linux OS agent, you can monitor other aspects of the system, such as the overall CPU, memory, and disk.
The offering determines which monitoring agents are available for installation. For a list of the agents included in each offering, see Capabilities.
For a list of the agents that run on AIX® and Solaris systems, see Installing agents on UNIX systems.
Before you begin
Download the agents. See Downloading your agents and data collectors.
Review the information in System requirements to make sure that you have met the requirements for the agents you plan to install.
- For AIX systems, see Preinstallation on AIX systems.
- For Solaris systems, see Preinstallation on Solaris systems.
About this task
You can install monitoring agents as a root user or non-root user. If you do not have root privileges and you want to install a monitoring agent, you can install the agent as a non-root user, see Installing agents as a non-root user. Also, you can install the agent as a non-root user if you are a host administrator and you do not want to run the monitoring agent as a root user. Installation flow is the same as for a root user.
Agent coexistence is supported. You can install IBM Cloud Application Performance Management agents on the same computer where IBM Tivoli® Monitoring agents are installed. However, both agent types cannot be installed in the same directory. For more information about agent coexistence see Cloud APM agent and Tivoli Monitoring agent coexistence.
Procedure
What to do next
- If you are using a forward proxy because your firewall does not allow transparent outbound HTTPS connections to external hosts, you must edit the agent environment configuration file. For instructions, see Configuring agents to communicate through a forward proxy.
- If you upgraded an agent from a previous version, identify any reconfiguration or migration tasks that you must complete before logging in to the Cloud APM console. For information about those tasks, see Upgrading your agents. After an upgrade, you must restart any agent that is not both automatically configured and started by the installer.
./name-agent.sh start
For information about the monitoring
agent commands, including the name to use, see Using agent commands. For information about which agents are started
automatically and manually, see Agent and data collector deployment.After an upgrade, you must restart any agent that is not both automatically configured and started by the installer.
- If you are not logged in, follow the instructions in Starting the Cloud APM console.
- If you want to view managed systems from your IBM Tivoli Monitoring domain in the Application Performance Dashboard, complete the tasks that are described in Integrating with IBM Tivoli Monitoring V6.3.
- Restart the apmui service on the Cloud APM server so that agent online help updates are
displayed in the Cloud APM console. The apmui service is restarted by using the
apm restart apmui
command.