If you enable resource monitoring, you must specify the
sources of resource monitoring data. A cloud schedule can contain resource monitoring locations that
can be in the local premises, in the cloud location, or in both the places.
Procedure
- Open a schedule for editing.
- At the bottom of the Resource Monitoring page, click Add. You might need to scroll
down in the view. The Create and manage
configurations wizard opens.
- Do one of these steps:
- To create a resource monitoring location, click Create new resource monitoring location.
- To add an existing location or to create a resource monitoring
location that is based on an existing location, click Create
or add a resource monitoring location from an existing source.
- Type an IP address or the fully qualified host name. This address or host name is for the node
to monitor, not the Tivoli
Enterprise Monitoring Server. The IP address can be of a computer that is in the cloud. You can choose the types of data sources.
- Select from these data sources:
- Apache HTTP Server Monitoring
- Apache Tomcat Application Server Monitoring
- IBM DB2 Monitoring
- IBM Tivoli Monitoring
- IBM WebSphere PMI Monitoring
- JBoss Application Server Monitoring
- JVM Monitoring
- Oracle Database Monitoring
- Oracle WebLogic Server Monitoring
- SAP NetWeaver Web Application Server Monitoring
- SNMP Monitoring
- UNIX rstatd monitor
- Windows Performance Monitor
You can select multiple types of data sources, but you must
configure each one separately. You cannot collect Windows Performance Monitoring data from
a computer that is running the Linux operating system. Also, you cannot collect Windows Performance Monitoring data if your
workbench is running the Linux operating system. In other words, to collect Windows Performance Monitoring data, the
workbench and the node to monitor must both be running the Windows operating system.
What to do next
Configure the data sources.