...

• An event matches criteria defined in an action rule.
• An action fires an escalation policy.
• The Escalation policy initiates email or some other action.  The email action calls a 'contact' variable.
• The contact variable is resolved to an email address or multiple addresses.
• Emails are sent via an associated email server.

Related Wiki Articles

• Event Actions and Escalation
• Email templates in opEvents
• NMIS8 Contacts

Configuration

Declare an Email Server

...

%hash = (
  'contact1' => {
    'Contact' => 'Contact1',
    'Phone' => '',
    'DutyTime' => '06:20:MonTueWedThuFri',
    'Level' => '(Fatal|Critical|Major|Minor|Warning|Normal)',
    'TimeZone' => '0',
    'Pager' => '',
    'Mobile' => '5555551234',
    'Location' => 'default',
    'Email' => 'nobody@localhost',
                'EmailTemplate' => 'default',
  }
); 

 For more information about Contacts.nmis see this page: NMIS8 Contacts

Create an Escalation Policy

...

This example states that 10 seconds after the policy is invoked it will email and email addresses associated with 'Contact1' if the priority of the event is greater than zero.

For more information about Escalation policies see this page:  Event Actions and Escalation

Create an Action

An action is required that will invoke the escalation policy.  Actions are also created in 'policy' section of EventActions.nmis.  The opEvents administrator will determine where best to place the rule with EventActions.nmis.  Here is one example.

...

In this example any event with a priority equal to or greater than 5 will fire the escalation policy 'exampleEmailPolicy.  Because the BREAK attribute is set to false, any rules following this one in the same hierarchy will continue to be processed.

Fore more information about action policies see this page:  Event Actions and Escalation

Verification