23.4 MESSAGE PROCESSING
Similar to OVOU, OVOW uses intelligent agents to monitor events and collect information for further processing. Event sources include log files, SNMP events, performance metrics and messages generated externally using the message API. The events are processed, presented, and acted upon either automatically or with operator assistance. In order to process the event, the agent is directed through configuration policies what events to monitor and process.23.4.1 Policies, Actions and Tools
A policy contains rules that determine what objects to monitor. The object is the source of an event that would trigger further action by the agent. For example, the policy might direct the agent to suppress an event or generate a message as a result of the object exceeding a specific threshold. Messages that are processed and filtered based on attributes such as node, application, object, severity, and descriptive text are forwarded to the server and appear in the active message browser. Actions are planned responses to the specific event. An action can be performed automatically at the managed node or with operator assistance after the message arrives on the server. Built-in tools such as executable commands give the user more flexibility to respond to problems.Finding the root cause of an event is important in analyzing and making a problem determination. The service console allows an operator to drill down on a service to view the root cause of the problem and or take further action to resolve the problem. |
لطفا منتظر باشید ...
