Events
A journal of JSON events written by your flows, searchable and filterable
A metric keeps a number over time; an event keeps a fact: a person detected, a machine cycle completed, an alarm acknowledged — with its whole JSON context. Flows write events, the Events page finds them.
The Event log node
The Event log node stores msg.payload (any JSON) as an event in OpenObserve, then
passes the message through unchanged.
| Setting | Role |
|---|---|
| Stream | The event stream name (events by default, stored in ev_events): one stream per use, for example detections or cycles |
| Level | Debug, Info (default), Warning or Error |
| Message | Optional short text (at most 500 characters) shown in the list |
Typically: Object detection → Event log to keep every person a camera detects, or a boolean Calc → Event log to trace threshold crossings.
The Events page
Monitor › Events lists the Events written by your flows: Time, Level, Message, Topic, Flow and Node, with the JSON payload expandable on each row. Filter by Stream, by level (All levels…), by Period (Last hour, Last 24 hours, Last 7 days or Custom period) and full text (Search in events…).
The Stream list also offers ev_controls, the journal of commands sent from
dashboards and annotations (who, which value, from which surface), once a
control has been operated.
No event? Either no Event log node has written for the organization yet, or OpenObserve is not configured on this server. Retention follows the organization's OpenObserve retention.
Notification deliveries have their own journal, in the Events tab of the Notifications page.