Archived alarms

You need: Archived alarms — view. Exporting needs the metrics export permission. hub_manager holds the view; chain-wide export is typically admin.

Archiving an alarm doesn't delete it. Archived alarms are kept and can be reviewed later — the history is where you find patterns that no single shift reveals.

Where to find them

Archived alarms live with Metrics, not with the live Hub board. That split is deliberate: the Hub is for what needs acting on now, Metrics is for what happened.

What the history is for

Question How the history answers it
Is this store always like this? Compare its alarm volume against comparable stores over the same period
Is our threshold sensible? An alarm archived in seconds every time is firing too readily — see Alarm settings
Did that change help? Compare the weeks either side of a configuration change
Which alarms does nobody act on? An alarm type that is always archived immediately, with nothing else happening, is noise

Tuning thresholds from history

This is the main reason the history exists. Before changing a threshold in Alarm settings, look at what that alarm actually did over a representative period — a fortnight, not one bad shift.

Two patterns are worth acting on:

Remember thresholds are chain-wide: a change made to quieten one store changes every store.

Exporting

The history can be exported for analysis outside the console. Export is a separate, higher permission than viewing, because an export leaves the console's access controls behind entirely.

An exported file is no longer scope-filtered. Whoever opens the spreadsheet sees everything in it, regardless of what they could see in the console. Treat exports accordingly, and prefer sharing a conclusion over the raw file.


Created 2026-09-17 16:28:40 UTC by Fran Sanchis
Updated 2026-09-18 07:48:29 UTC by Fran Sanchis