Alert Types Reference

PEEK supports 9 alert types. This page describes each one, its configuration, and when it fires.

Device Offline

Triggers when a specific device stops sending data and transitions to offline status. Must be scoped to an individual device.

Scope: Single device
Create from: Device detail page
Auto-resolves: Yes — when device sends a message

Device Online

Triggers when a specific device comes back online after being offline. Useful for confirming recovery.

Scope: Single device
Create from: Device detail page

Fleet Offline Percent

Triggers when the percentage of offline devices in your fleet exceeds a threshold. For example, alert when more than 20% of devices are offline.

Scope: Fleet-wide
Config: Percentage threshold (e.g., 20%)
Create from: Alerts tab

Low Message Rate

Triggers when the message rate for a device or fleet drops below a specified threshold (messages per minute).

Scope: Device or fleet-wide
Config: Minimum messages per minute

High Message Rate

Triggers when the message rate exceeds a specified threshold. Useful for detecting runaway devices or unexpected burst traffic.

Scope: Device or fleet-wide
Config: Maximum messages per minute

New Device

Triggers when PEEK discovers a device it has not seen before. Useful for tracking fleet growth or detecting unexpected devices.

Scope: Fleet-wide
Config: None — fires on any new device
Create from: Alerts tab

Field Threshold

Triggers when a numeric field in a message payload crosses a boundary. Supports six comparison operators.

Scope: Device or fleet-wide
Config: Field path, operator, threshold value
Operators: > < >= <= = !=

Example: Alert when temperature is greater than 45.

Field Match

Triggers when a payload field matches a specific string value. Useful for catching error codes or specific states.

Scope: Device or fleet-wide
Config: Field path, match value

Example: Alert when status equals error.

Payload Size

Triggers when a message payload size exceeds or falls below a threshold (in bytes). Useful for detecting abnormally large or truncated messages.

Scope: Device or fleet-wide
Config: Operator, size in bytes