...
A more in-depth discussion of event correlation rules is covered HERE: Event Correlation
Add Troubleshooting Buttons
It is helpful to include troubleshooting tools into opEvents so that I can stay in a single window while working an issue without having to open separate command line windows or other tools. One way of doing this is by adding some simple Programmable Buttons that can be turned on/off based on various device or event criteria, or enabled all the time for every event.
The basic of configuring this feature are covered in detail HERE: opEvents Programmable Button Actions
For a starting point I usually include buttons to run a Ping, MTR, NMIS9 Polling Summary, and open a help desk ticket.
Remember that these buttons call entries located in the "script" section of /usr/local/omk/conf/EventActions.json, which can be edited interactively through the opEvents' GUI by selecting System -> Edit Event Actions from the menu.
More on Event Actions can be found HERE: Event Actions and Escalation
Setup Summary Reports
opEvents automatically creates detailed reports of all events processed on a Daily, Weekly, and MOnthly basis. These reports can be emailed upon creation with the Daily Report going to the engineering Tiger Team/NOC Manager, and Weekly to Architect and Department Head.
Report Configuration is covered in detail HERE: opEvents Summary Reports