How Health Rolls Up

更新日期: 2010年8月

適用於: Operations Manager 2007

The Operations Manager Management Pack views the services of Operations Manager as a hierarchy. The health of each level depends on the health of the level below it. The top level is the Operations Manager Management Group, which you can use to gauge the health of your monitoring infrastructure. At the lowest level are the counters, events, scripts, and service states that the Operations Manager monitors. When a number of these items changes state, the level above changes state to match; in other words, the health of the lower level rolls up to the level above it.

At the lowest level, unit monitors check the operational state of objects. For example, the agent manager includes unit monitors that assess aspects of the configuration health service, such as whether an agent installer failed to start, failed to install, or already exists. Unit monitors roll up to either aggregate or dependency rollup monitors.

An aggregate rollup monitor reflects the state of a collection of unit monitors, dependency rollup monitors, or other aggregate rollup monitors. For example, the unit monitors for the configuration health service roll up to the configuration health service aggregate monitor. The aggregate rollup monitor can then specify the health state and generate an alert.

A dependency rollup monitor rolls up health states from targets linked by either a hosting or a membership relationship that is defined in the Management Pack. The dependency rollup monitor can be used to group other monitors to set the health state and generate alerts. For example, you can use a dependency monitor to check the availability of multiple management servers and then roll up their health into a management server group.

89aef66a-4845-43e6-b199-cb62f89cc9f1

社群新增項目

顯示: