Managing events with PATROL Event Manager

The PATROL Agent uses its PATROL Event Manager (PEM) engine for event management. Through the PEM Engine, the PATROL Agent provides the following event management services:

• View, filter, and sort events
• Define and access event knowledge through event catalogs 
  An event catalog is a subset of a PATROL KM.
• Trigger events from PSL, a C program, the command line, or a PEM Console
• Send ActiveX scripts to the PATROL Scripting Host to run (for Windows only) with the PSL execute function 
  For more information about using the PATROL Scripting Host, see the PATROL Script Language Reference Guide.
• Configure commands (standard or user created) for execution by the agent when an event is triggered 
  When the event is triggered, the agent checks the event catalog to determine whether a Notification command is defined. If it is, the agent executes the command.
• Schedule commands (standard or user created) for execution by the agent when an event is escalated 
  When the event is escalated, the agent checks the event catalog to determine whether an Escalation command is defined. If it is, the agent runs the command.
• Store events, even when no console is registered to receive them
• Manage events through acknowledge/close/delete
  Acknowledging an event can trigger commands (standard or user created). The PEM Engine is configured to determine which events trigger which commands for execution by the PATROL Agent. The agent checks the event catalog to determine whether an Acknowledge command has been defined. If it has, the agent runs the command when the event changes status to acknowledged. 
  After an event is marked for deletion, it is still visible in Event Manager Window until enough events are generated from the object resulting in a flush from the event cache to disk. When the event is flushed to disk, it is not visible.
• Generate reports of event statistics
• Archive events
• Send SNMP traps when an event that is configured with SEND_TRAP is triggered
• Make requests of external SNMP Agents and listen for SNMP traps (SNMP management functions)
• Respond to SNMP requests from external SNMP managers and send SNMP traps (SNMP Agent functions)

The following figure shows how the PEM engine works with other PATROL components:

Accessing PEM engine

You can access an agent's PEM Engine in the following ways:

• From the PATROL Console, PEM Console for UNIX, or any of the PATROL Integration products
• From any PATROL KM loaded on the Agent by using the PATROL Script Language (PSL)
• From a C program, using the PATROL API
• From the command line, using the PATROL Command Line Interface

Event management services

For additional information refer to the following documents:

• Refer to the BMC PATROL Console for Microsoft Windows
• Refer to the BMC PATROL Console for Unix User Guide
• Refer to the PATROL Script Language Reference Manual
• Refer PATROL components and Files used by PATROL Agent to determine methods available for requesting event management services from the PEM engine.