To view the latest 11.3.x version, see  PATROL Agent 11.3.02 Open link .

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

To request this service...

For PATROL Console a

PEM Console for UNIX b

PATROL API c

For PSL d

For Command Line

Access event knowledge

Event Editor

N/A

PemnGetEvent Class()
PemnGetEvent ClassList()

event_catalog _get()

PatrolCli event get PatrolCli event class

Archive events and transfer files

N/A

N/A

PemnEvent Archive()

event_archive()
remote_file_transfer()

PatrolCli event dump

Define event knowledge

Event Editor

N/A

PemnDefine EventClass()
PemnSetEvent ClassCmd()

N/A

N/A

Display events, event Diary, and event Expert Advice

Event Details window Event Diary window Event Expert Advice window

Event Details window Event Diary window Event Expert Advice window

PemnAddDiary()
PemnReceive()

event_query() event_range_query()

PatrolCli event listen
PatrolCli event query

Filter and query events

Event List window

Event List window

PemnReceive()
PemnEvent RangeQuery()
PemnEvent Query()

event_range_query()
event_query()
remote_event_query()

PatrolCli event query

Manage events (for example, with acknowledge/close/delete)

Event List window

Event List window

PemnEvent Manage()
PemnEvent RangeManage()

event_range_manage()

PatrolCli event class
PatrolCli event delete
PatrolCli event acknowledge

Obtain a report on Event Statistics

Event Repository window

Event Repository window

PemnGetReport()

event_report()
event_check()

PatrolCli event report

Schedule events

N/A

N/A

PemnEvent Schedule()

event_schedule()

N/A

Sort events

Event List window

Event List window

N/A

N/A

N/A

Trigger events specific to your application, events specific to your KM, or user events

N/A

Event Trigger dialog

PemnSend()

event_trigger()
event_trigger2()
remote_event_trigger()

PatrolCli event send

For additional information refer to the following documents:

Note

 Not all PATROL Integration products share the same functionality.

Was this page helpful? Yes No Submitting... Thank you

Comments