opEvents uses its own set of numeric priorities for events, ranging from 0 to 10. This priority value is saved in the priority event property.
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 | opEvents Priority | NameSyslog | NMIS Level | Email Priority | |
|---|---|---|---|---|---|
| 0 | debugdebug (7) | n/a | low | ||
| 1info | 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 | errorerr (3) | Minor | normal | |
| 6 | major | criticalcrit (2) | Major | high | |
| 7critical | alert (1) | Critical | high | ||
| 8 | fatal | emergencyemerg (0) | Fatal | high | |
| 9 | emergencyemerg (0) | n/a | high | ||
| 10 | catastrophic | emergency emerg (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.
From version 2.2 onwards, opEvents also (re)sets the level event property on event creation (computed from the priority and substituting the nearest available level name for untranslatable priorities, e.g. 4). Please note that this is purely for display purposes; opEvents bases any decisions exclusively on the priority value.