opEvents uses its own set of numeric priorities for events. As events generally originate from external sources with their own priority concepts, a bit of translation is required. The following table describes the mappings between event priorities in opEvents and related services: how syslog and email messages sent by opEvents are marked, and how events sourced from NMIS are classified.
| Priority | Priority Name | Syslog | NMIS Level | Email Priority |
|---|---|---|---|---|
| 0 | debug | debug (7) | n/a | low |
| 1 | info | info (6) | n/a | log |
| 2 | normal | notice (5) | Normal | low |
| 3 | warning | warning (4) | Warning | normal |
| 4 | n/a | n/a | normal | |
| 5 | minor | error (3) | Minor | normal |
| 6 | major | critical (2) | Major | high |
| 7 | critical | alert (1) | Critical | high |
| 8 | fatal | emergency (0) | Fatal | high |
| 9 | emergency (0) | n/a | high | |
| 10 | catastrophic | emergency (0) | n/a | high |
opEvents' standard parser rules will only generate event priority numbers in the range of 0 to 10 (inclusive), but it's generally ok to use numbers above 10. From version 2.0.8 onwards opEvents replaces negative priority numbers by priority 0.