Browse documentation
Reviewing alert history
Every notification JOATOS fires — and every clear — is recorded in the alert history, so you can see what happened, when, and whether it was delivered.
Where to find it
- Org-wide: in Settings, under Alerts, open History.
- Per device or server: the same history, filtered to that host, appears on its detail page.
What each row shows
| Column | Shows |
|---|---|
| Time | When the notification fired |
| Target | The device or server (and its site) |
| Condition | A readable detail, e.g. DOWN for 8 minutes, CPU at 94%, Disk /var at 97% |
| Event | ALERT or CLEAR — with the tier for escalations (e.g. ALERT T1) |
| Profile | The alert profile that fired |
| Delivery | Sent, Failed, No SMTP, or No recipients (hover a failure for the error) |
Each channel that fires is its own row, so a single condition that emails and posts to Slack produces two entries.
Filtering
Narrow the list by:
- Event type — All, Alerts, or Clears
- Condition — Down, CPU, Memory, Disk, Syslog, or Trap
- Delivery status — Sent, Failed, No SMTP, or No recipients
Results are paged (50 per page).
Reading delivery status
- Sent — delivered successfully.
- Failed — the channel returned an error (hover for detail).
- No SMTP — an email profile fired but no SMTP server is configured.
- No recipients — the profile had no one to notify.
Retention
History is kept for 90 days by default. An administrator can change the retention window (7–365 days); older entries are cleaned up automatically.
Notes & tips
- Use the Delivery column to catch misconfigured channels — repeated No SMTP or Failed rows point straight at what to fix.
- The per-host history on a device or server page is the quickest way to see an individual system's alert timeline.