Configuration setup for self monitoring of probes

Probes can be configured to generate statistical data that can be used to assess system performance and to help calculate return on investment.

The following figure shows the configuration setup for probe self monitoring.

Figure 1. Configuration and data flow for probe self monitoring
This figure shows how statistics data for probes can be collected and processed.

The configuration flow is as follows:

 1 
Usage and resource information is captured together with raw data that is sent to the probe.
 2 
The probe processes the usage and resource information in order to calculate performance metrics, and to generate ProbeWatch Heartbeat events that are populated with these metrics. The probe also processes the raw data in order to generate generic (standard) events.

Both sets of events are forwarded to the ObjectServer.

 3 
ObjectServer automations are used to produce a basic textual report that summarizes the statistical information generated by the probe .
 4  and  5 
The generic event data and ProbeWatch Heartbeat events can optionally be exported from the ObjectServer into Tivoli® Data Warehouse by using a relational database management system (RDBMS) gateway. These metrics can then be used for subsequent reporting in Tivoli Common Reporting.
Note: These steps (4 and 5) are outside the scope of the probe self-monitoring functionality provided by Tivoli Netcool/OMNIbus. Integration with IBM Tivoli Monitoring (which provides Tivoli Data Warehouse) and additional configuration will be required for this additional reporting.