Key Monitoring Scenarios

更新日期: 2010年8月

適用於: Operations Manager 2007

The Operations Manager Management Pack monitors the availability, configuration, performance, and security of the Operations Manager agents, services, workflow, and database. The management pack monitors the following key scenarios:

  • Active Directory integration

  • Agent health and remediation

  • Agent management and recovery

  • Core System: secure storage—password expiration

  • The health of the Health Service for agents and servers

  • Operational database health

The following table describes these monitoring scenarios.

 

Scenario Description

Active Directory integration

This scenario monitors the LDAP module for Active Directory integration agent assignment.

Agent Health

This scenario checks agents for out-of-date configurations from the perspective of the agent. When the configuration is at the warning or critical level, the monitor logs the event. The Health Service rolls up the health of the agents and alerts you when the configuration of a threshold of agents is out of date.

Agent management and recovery

The Health Service Watcher checks the heartbeat of agents and warns you when they fail. You can disable the monitor for managed clients or for a management server. By using the management pack, you can perform the following actions:

  • Repair the agent by automatically reinstalling it

  • Repair the agent by manually reinstalling it

  • Check the Health Service Windows Service State

  • Query the service state and the configuration

  • Ping the computer by using Internet Control Message Protocol (ICMP)

  • Recover and diagnose the agent by using the Automatic Agent Management Account Run As profile

  • Remotely enable and restart the health service

  • Remotely restart the health service

Core System: secure storage—password expiration

This scenario checks the secure storage's public key and configuration. The monitor alerts you about password expirations and configuration errors of Run As accounts.

The health of the Health Service for agents and servers

This scenario includes the following monitors for the Health Service:

  • Handle count of the MonitoringHost.exe process. When the average Handle Count counter for the MonitoringHost.exe process exceeds the configured threshold, a rule automatically restarts the Health Service on agents.

  • Private bytes of the MonitoringHost.exe process. When the average Private Bytes counter for MonitoringHost.exe exceeds the configured threshold, a rule automatically restarts the Health Service on agents.

  • Handle count of the HealthService.exe process. When the monitor detects that the average Handle Count counter for the HealthService.exe process exceeds the configured threshold, the monitor triggers a recovery to automatically restart the Health Service on agents.

  • Private bytes of the HealthService.exe process. When this monitor detects that the average Private Bytes counter for HealthService.exe exceeds the configured threshold, it triggers a recovery to automatically restart the Health Service on agents.

  • Action Account Configuration State. This monitor checks the configuration state of the action account and alerts you to errors.

  • System Rules Loaded State. This monitor checks that the rules are loaded. If an aggregation of the rules is not loaded, the monitor alerts you.

The health of the operational database

This scenario monitors the free space threshold of the operational database and alerts you if the monitor is in a warning or critical state. If the operational database runs out of space, the monitoring of other components and services can be interrupted.

社群新增項目

顯示: