For state tracking opEvents then combines the node name and the values of
element into a lookup key, and associates that key with the
Any repeat events with the same lookup key and the same state value are ignored.
Stateful Deduplication, Forwarded Events and Reorder Protection
If you use an Event Action or Escalation Policy with
create_remote_events to forward events to another opEvents server elsewhere, then you might occasionally find that such forwarded events arrive out of order, i.e. an earlier 'down' event might be received after the later 'up' event. This can happen because of network congestion, action processing on the sending side being asynchronous and subject to process limits and similar reasons.