Event Policies and Event Notifications Overview
Understanding Event Policies and Event Notifications
To diagnose a fault or error condition on a device, you need relevant information about the state of the platform. You can derive state information from event notifications. Event notifications are system log messages and SNMP traps. A Junos OS process called the event process (eventd) receives event notifications—henceforth simply called events— from other Junos OS processes.
Timely diagnosis and intervention can correct error conditions and keep the device in operation. After the eventd process receives events, event policies instruct the eventd process to select specific events, correlate the events, and perform a set of actions. These actions can either help you diagnose a fault or take corrective action. For example, the eventd process can upload device files to a given destination and issue operational mode commands.
Events can originate as SNMP traps or system log messages. The event process receives event messages from other Junos OS processes, such as the routing protocol process (rpd) and the management process (mgd). Depending on the custom event policy you configure, eventd listens for specific events and in response to these events might create a log file, invoke a Junos OS command, or invoke an event script. When an event script is invoked, event details are passed to the event script in the form of XML inputs.
Figure 1 shows how the event process (eventd) interacts with other Junos OS processes.
Benefits of Event Policies
Event policies provide the following benefits:
Improve network reliability and maximize network uptime by automatically responding to system events, including system log messages, SNMP traps, chassis alarms, and internal timers
Shorten troubleshooting time and speed time to resolution for network issues by automating troubleshooting tasks
Reduce the time required for manual system monitoring and intervention