Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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, notify, and generate automated actions based on rules that make sense for your environment.

...

  1. Configure in opEvents by following the Wiki guide to assist in setting up your Contacts - Configure Contacts
  2. Alternatively create Contacts within the NMIS GUI.
    a. Navigate to NMIS menu -> Setup -> Contact Setup
    b. Click 'add' next to Action > add
    c. Enter relevant information, click Add at the bottom to confirm.

Creating your

...

Policy and Action

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. Create a policy that ensures that the engineers you want to alert by email, text, etc. are only alerted by the severity of the event that makes sense within your organization. Doing this reduces event noise allowing your team to quickly identify the important events.

  1. Follow the basic example of creating a new Escalation Policy - Escalation Policy example
  2. More detailed Escalation Policy example examples and information - Event Actions and Escalation

...