Threshold Editor | Zyeon UI

status="ready" · 7 live rules. Every edit is a real write: change a threshold and the "would have paged" line under it recomputes from 24 h of recorded samples. Rule 4 is stored with its band upside down (lower 4000, upper 800) — the editor reads it swapped, says so, and only stores the correction when you press "Apply fix". Rule 5 carries a negative fractional threshold (-2.5): type "-1.5" into it one character at a time, which a controlled <input type="number"> cannot do. Rule 6 asks for a 36 h wait against a 24 h history, and rule 7 watches a metric with no samples at all

Alert thresholds

7 rules · 6 armed · 10 pages over the last 24h · 2 cannot be replayed

Armed
When%for
would have paged 4× over the last 24h · 1h 35m over the line, longest run 25m · 2 shorter blips filtered out by the 15m wait
Armed
Whenmsfor
would have paged 2× over the last 24h · 1h over the line, longest run 30m · 1 shorter blip filtered out by the 10m wait · one breach was still building when the samples ran out
Armed
When%for— the first breaching sample pages
would have paged 2× over the last 24h · 15m over the line, longest run 10m
Armed
Whenreq/minfor
- Band bounds are stored upside down (lower 4000, upper 800), which as written can never be left. Read as 800 … 4000; "Apply fix" stores it that way.
would have paged 2× over the last 24h · 45m over the line, longest run 25m · 1 shorter blip filtered out by the 10m wait
Off
When%for
If armed: would have paged 1× over the last 24h · 1h 40m over the line, longest run 1h 10m · 1 shorter blip filtered out by the 1h wait
Armed
Whensfor
The recorded history covers 24h — less than the 36h this rule waits for, so it never had the chance to fire. That is not the same as never firing.
Armed
Whenmsfor
No recorded samples for Cold start p99, so this rule cannot be replayed here.

7 rules held by this demo — the component stores nothing of its own.

status="ready" · no onChange — a read-only audit view. Every control renders disabled and the add / delete / fix buttons are not rendered at all, so nothing looks clickable that would do nothing

Alert thresholds

7 rules · 6 armed · 10 pages over the last 24h · 2 cannot be replayed

Armed
When%for
would have paged 4× over the last 24h · 1h 35m over the line, longest run 25m · 2 shorter blips filtered out by the 15m wait
Armed
Whenmsfor
would have paged 2× over the last 24h · 1h over the line, longest run 30m · 1 shorter blip filtered out by the 10m wait · one breach was still building when the samples ran out
Armed
When%for— the first breaching sample pages
would have paged 2× over the last 24h · 15m over the line, longest run 10m
Armed
Whenreq/minfor
- Band bounds are stored upside down (lower 4000, upper 800), which as written can never be left. Read as 800 … 4000; "Apply fix" stores it that way.
would have paged 2× over the last 24h · 45m over the line, longest run 25m · 1 shorter blip filtered out by the 10m wait
Off
When%for
If armed: would have paged 1× over the last 24h · 1h 40m over the line, longest run 1h 10m · 1 shorter blip filtered out by the 1h wait
Armed
Whensfor
The recorded history covers 24h — less than the 36h this rule waits for, so it never had the chance to fire. That is not the same as never firing.
Armed
Whenmsfor
No recorded samples for Cold start p99, so this rule cannot be replayed here.

status="empty" · no rules configured yet, but the metric menu and the recorded history are still there — so "Add your first rule" produces a rule that can be previewed straight away

Alert thresholds

No thresholds yet

A rule watches one metric, waits for the breach to hold, and only then pages someone. Add one and the recorded history will tell you how often it would have gone off.

status="loading" · skeletonRows={4} — the placeholder cards keep the ready layout (header row, control row, preview line) so nothing jumps when the data lands; the pulse stops under prefers-reduced-motion

Alert thresholds

status="error" · "Try again" only renders when onRetry is passed, and clicking it runs a real error → loading → ready

Alert thresholds

Couldn't load the thresholds

The rules were not read, so nothing here is a statement about what is armed.

Current status: error