Concept
opEvents generates a variety of events and depending on the size and health of your network there may be thousands of events a day. These events can vary in importance from warnings of high CPU usage to critical failures of hardware. It is not necessary to send email notifications to every engineer on staff in regards to minor events. If every event is notifying everyone on staff then soon there will be less attention to these events making it easier to overlook the critical ones. opEvents gives you the ability to create policies and generate automated actions based on rules that make sense for your environment.
NOTE - This guide requires you to be familiar with Perl and Linux operating systems. Helpful resources on these topics can be located here - Learning and Understanding Perl and here - Introduction to the Linux Operating System
Creating your policy
The action policy is configured in conf/EventActions.nmis, primarily in the section named policy. The policy consists of any number of nested if-this-then-that clauses, which specify the conditions an event must conform to and what actions to take in case of a match. Further configuration sections specific to particular actions can be present in the same file.