...
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. Use the examples within the links below as well as the default policies within the EventActions.nmis file json (EventActions.nmis for NMIS 8) file to help create a policy right for your environment.
...
The opevents-cli.exe utility found in /usr/local/omk/bin may be used to create a test event. Create an event that will match a previously configured action rule. For example:
...
| Code Block |
|---|
[root@opmantek conf]# /usr/local/omk/bin/opevents-cli.exe act=create-event node=testNode4 stateful=node state=down event="Node DOWN" priority=5 5997bb8cce2c2e6d9453c101 |
This command will return an event ID. Go to the event context page for this event. In the Actions section of the page there should be an entry stating an email was successfully sent. Keep in mind that this entry will not be present until the flap window and escalation timers have elapsed.
...