Alerts & Notifications
Define rules to get notified when things go wrong (or right) in your fleet.
How Alerts Work
An alert in PEEK consists of:
- • Type — what condition to watch for (9 types available)
- • Configuration — parameters specific to the alert type (thresholds, field names, etc.)
- • Scope — fleet-wide or scoped to a specific device
- • Cooldown — minimum time between repeated triggers to prevent notification spam
Creating an Alert
There are two places to create alerts:
- • Alerts tab — for fleet-wide alerts (e.g., "New Device", "Fleet Offline %")
- • Device detail page — for device-scoped alerts (e.g., "Device Offline" for a specific device)
Alert Events
When an alert's condition is met, PEEK creates an alert event. Each event has a status:
| Status | Meaning |
|---|---|
| Active | The condition is currently triggered and unresolved |
| Acknowledged | A team member has seen this event and is handling it |
| Resolved | The issue has been resolved (manually or automatically) |
Note
Device Offline alerts are automatically resolved when the device comes back online and sends a message.
Cooldown Periods
Each alert has a configurable cooldown period (in minutes). After an alert fires, it will not fire again until the cooldown has elapsed, even if the condition is still met. This prevents notification spam from noisy or flapping conditions.
Notification Channels
When an alert fires, PEEK can notify you through:
- • Email — sent to your account email
- • SMS — for critical alerts (available on Pro plans)
- • Discord webhook — post alerts to a Discord channel
For a complete reference of all alert types and their configuration options, see Alert Types Reference.