Resource Pool monitor
Resource Pool Monitors are useful for aggregating metrics across monitor instances. They work on the data already collected by adapters. They can create complex combinations of metrics and monitor higher-level abstractions such as pools or clusters. Creating a monitor at this level enables setting thresholds that are otherwise not possible.
Resource Pool monitor is a grouping of monitor instances. For example, the adapter for BMC PATROL would create monitor instances for the corresponding BMC PATROL Monitoring Solution. The value for each of the attributes monitored by the Resource Pool monitor is calculated based on the latest value from each of the underlying instances.
Resource Pool Monitor is available only on the local agent (local agent on Infrastructure Management Server).
A few examples of when a Resource Pool monitor can be created:
- You have a pool of Web servers. Although there is a monitor for each Web server in the pool, it has limited use because the monitor is at a granular level. To learn how the pool as a whole is performing is desirable, and therefore, you would like to have a monitor that reports stats at the pool level. You actually want to know how the pool is performing as an aggregate of all the Web servers as opposed to knowing how each Web server is performing.
- The scenario given above can also be applied to application server clusters and other applications that are used in a pool fashion.
- You have an application that consists of many processes. Although it is useful to monitor each process separately, it is also desirable to know how all the processes together are performing (in terms of performance metrics). Aggregating all the performance metrics enables you to easily see application-level performance metrics as opposed to always seeing the individual components.