Alert history and notes¶
Two pages look back at what happened:
| Page | Answers | Who can see it |
|---|---|---|
| Alert History | Who was notified, how, and whether it got through or was acknowledged | Users with the View Alert History role |
| Alert Notes | When each alert set and cleared, and what your team recorded as the cause and resolution | Everyone on the account |
Alert History¶
Alerts → Alert History lists every text, email and call Whisker.io sent: alarms, acknowledgements, clears, fallbacks and tests. Use it to answer "was Luis actually texted at 2 a.m.?" or "who acknowledged the freezer alarm?".
The tab only appears if you hold the role assigned to View Alert History under Control Panel → Roles. See Roles and permissions.
Filter¶
- Date range: Today, Last 7 days, Last 30 days, or Custom range with start and end dates.
- All locations, All devices, All alerts, All contacts: narrow to one of each. The device list follows the location, and the alert list follows the device.
- Channel: Text, Email or Voice. (This is how the message was sent, not the device channel.)
- Result: Queued, Delivered, Failed, No answer, Busy, Voicemail, Answered, Acknowledged or Skipped.
The filters are kept in the page address, so you can bookmark a filtered view or paste it into an email to a colleague.
Read the grid¶
| Column | Contents |
|---|---|
| Time | When it was sent, in the location's time zone. Hover for UTC |
| Location, Device, Alert | What fired |
| Kind | Set (the alarm), Clear, Acknowledged-broadcast (the "acknowledged by" message), Fallback (sent because nobody acknowledged), Test |
| Channel | Text, email or voice |
| Contact | Who it went to |
| Result | What happened to it. Answered means the call was picked up but nobody pressed 1. Skipped means the person was passed over, for example because their number is invalid or they opted out |
| Acknowledged by | Who acknowledged the alarm, if anyone |
Click a row that belongs to an alarm to expand it and see every attempt made for that alarm, in order.
Note
Alert History starts from when schedule groups were introduced, plus the 90 days of text history before that. Older notifications are not available.
Export¶
Click Export CSV to download the current view (with your filters) as a spreadsheet file. The export is limited to 100,000 rows; if the button is disabled, narrow the date range or filters.
Alert Notes: documenting occurrences¶
Alerts → Alert Notes is where your team records the cause and resolution of every alert occurrence, turning the alert history into an operational log you can audit and export.
- Under Select Time Interval, set the start and end and click Set. It starts at today from midnight. "No Alerts History for this date range" means exactly that.
-
Every alert occurrence in the range loads into the grid:
Column Contents Location Name, Device Name, Alert Name What fired, and where Value The reading that set the alert Alert Activity Date When it fired, in the device's local time Current Alert Status Icon: still active, cleared, or snoozed Is Active Yes or No Cause / Cause Author What caused it, and who wrote that Resolution / Resolution Author What was done about it, and who wrote that Resolution Status ✔ once both Cause and Resolution are filled in, ✘ otherwise -
Four tabs regroup the same list: Alerts By Location (the default), Alerts By Date, Alerts By Current Status and Alerts By Resolution Status.
- To document an occurrence, open its row for editing, type in Cause and Resolution, and save. You'll see "Note Saved!". The author columns fill in automatically.
Tip
The Alerts By Resolution Status tab is a built-in to-do list: everything marked ✘ still needs its cause or resolution written up. Undocumented rows read Cause Unknown and No Resolution until someone fills them in.
The grid supports filtering, a column chooser, remembers your layout, and exports to Excel.
The device panel¶
For one device, its panel has Triggered Alerts (set right now) and Alerts History (past occurrences with set and clear times and values). See How alerts work.