Child pages
  • opEvents Normalised Event Properties

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: clarified new and deprecated properties, ie. stateful_eventids, trigger_eventids and changed content for eventids


Event PropertyDescriptionExample
interface_descriptionThe ifAlias (or Description) of the interface in question
  • only available with opEvents versions 2.0 and newer,
  • only for interface-related stateful events (i.e. element is an interface), 
  • and only if the node was refreshed or imported from NMIS with opEvents  2.0 or newer
authorityThe server name of the system that originated the event;
Optional, only relevant for remotely/API-generated events.
locationThe URI for this event at the originating server.
Optional, only relevant for remotely/API-generated events.
duplicateofList of Event IDs that this one is a duplicate of.
Only present when programmable suppression rules affected this event.
nodeslists nodes that caused this synthetic event. Only present if this is a synthetic event. 
eventidslist List of Event IDs that were involved in causing this synthetic event.
In (Only in opEvents versions 2.0.3 and newer to 2.2.1 this is also set for relationships between events,
e.g. for auto-acknowledged events the up event lists the down event's id here and vice versa.)
stateful_eventidsList of Event IDs that are related to this stateful event,
e.g. the preceding down event if this one is an up event and vice versa.
Only present in opEvents versions 2.4 and newer, and only if this event is stateful.


Unix time, until then the event is held back from processing for actions and policies1385079231
action_checkedHas the event been processed wrt. actions and policies?0 or 1
If an event triggered a script action that is set to save output,
then the script output (and the script's execution time) is stored in these properties.
syntheticwhether this event was created by a correlation policy action,
or because a watchdog expired
0 or 1

Deprecated as of opEvents 2.4, see trigger_eventids for replacement.

Event ID of the synthetic event that this event was a trigger for.
Only present in opEvents versions 2.0.4 and newerto 2.2.1, and only if a correlation policy action
identified this event as a trigger. If multiple policies apply, only the last trigger is stored.

watchdogwhether trigger_eventidsList of synthetic event IDs that this one is a trigger of.
Only in opEvents 2.4 and newer, and only if one or more correlation policy actions have identified this event as a trigger.
watchdogWhether this is a watchdog expiration event0 or 1
escalation_ageIf the event is or was subject to escalation, then this property indicates the
event's most recent escalation threshold. Note that this property is not cleared when
the event is acknowledged and escalation terminates.
60, 900 etc.
escalation_policyIf the event is or was subject to escalation, then this property lists the
event's most recently active escalation policy name.
Like the previous property, this one persists after escalation terminates.
notesa list of originator- and time-tagged comments for this event
(optional, supported in opEvents 2.0 and newer)
tag_<anything>These enrichment tags are controlled by your action policy, and have no special meaning
- with the exception of tag_kb_topic, which controls linking to online sources
(in opEvents 2.0.2 and up),
- and tag_servicePriority, which is shown with the event priority if present
(only in opEvents 2.0.4 and up)
status_historyA structured record of changes and activities related to the event.