Events

What an event is¶

An event is a lasting condition a rule found, from its start to its end:

Kind	Opens when	Closes when
Past a limit	the N-th reading in a row passes the rule's limit — the event starts at the first of them	a reading is back within the limit
Zone check	the N-th positioned reading in a row fails (or passes, as the rule says) its zone's check	a position on the other side
Sensor quiet	a sensor has sent nothing for longer than its class expects — the event starts when the silence passed the interval	the sensor reports again

While an event is open its rule fires no second time for that asset and sensor, its asset reads Alerting (or Stale), and the live layer counts it in open_events. A momentary trigger — a service status changed, a record approved — fires once and opens no event.

What closes it¶

Shown as	How
Cleared by its readings	a reading back within the limit, or the quiet sensor reporting again
Resolved by a member	someone who manages assets pressed Resolve
Closed when its rule was switched off or changed	the rule was switched off, deleted, or given something else to watch
Closed when its sensor was switched off	by its enterprise, by Haiyz, or because its asset was deleted
Closed when its sensor was deleted	its readings went with the sensor; the event stays

Only the first runs a rule's also when it clears actions.

Where events are¶

• Hyz Assets › Events — every event of the enterprise, newest first, filtered by enterprise, class and state (Open, Cleared), or by one asset.
• An asset's page › Events — its events and the firings that reached it.
• Every readings chart — the asset's, the sensor's, the dashboard's Readings series — draws each event of the sensors it shows as a band from its start to its clear.
• A rule's What it fired in Hyz Console links to each event.

An event's page¶

What it found says the condition in words (Temperature above 80 °C for 3 readings in a row), as it stood when the event began — it outlives a rule that is changed or deleted. Readings draws its sensor's readings over its span, a minute either side, and says whether they are kept. Its facts: state, kind, rule, asset, class, sensor, when it started and cleared, how long it lasted, its worst value, and how many readings it keeps. What its rule did lists its firings with each action's outcome, and Note holds what someone found or did.

The readings it keeps¶

Every reading of the event's sensor from the one that started it to the one that cleared it is kept — it does not expire with the retention while the event is kept, and a late reading that falls in its span is kept too. An event is kept until someone who manages assets deletes it.

On Haiyz Cloud the readings events keep have a budget of their own, 5 GB per enterprise. At 80% of it the enterprise's owners, administrators and asset managers are told, once each time it is crossed. At 100% a new event is still found, recorded and kept, but keeps none of its readings — its page says Not kept: the budget for kept readings was full when it began. On a self-hosted instance nothing caps them.

Resolve, note, delete¶

For whoever manages assets (owners, administrators, Asset managers):

• Resolve closes an open event as you. No also when it clears action runs, and the rule starts over for that sensor.
• Edit the note — up to 2 000 characters, for whoever reads the event next.
• Delete removes the event. Its readings expire again — those already past their time go at the next sweep — except those another kept event of the same sensor still spans. Deleting is refused while the enterprise is under a legal hold.

Resolving and deleting are written to the enterprise's audit trail.