Alerts
Alerts notify you when a metric crosses a threshold. You define conditions on any metric, and Plexus evaluates them in real time as data arrives.
Creating an Alert
- Go to Dashboards or Fleet in app.plexus.company (opens in a new tab)
- Click Alerts in the sidebar
- Click New Alert
- Configure the alert:
- Name — A descriptive label (e.g., "Motor Overheat Warning")
- Source — The device or source to monitor (or "All Sources")
- Metric — The metric name (e.g.,
cpu.temperature) - Condition — The comparison operator and threshold
- Channel — Where to send the notification
Alert Conditions
Each alert evaluates a single condition against incoming data:
| Condition | Description | Example |
|---|---|---|
| Above | Triggers when the value exceeds the threshold | cpu.temperature > 85 |
| Below | Triggers when the value drops below the threshold | battery.voltage < 3.2 |
| Equal | Triggers when the value matches exactly | motor.state == "error" |
| Outside range | Triggers when the value is outside a min/max range | pressure < 900 or pressure > 1100 |
| No data | Triggers when no data arrives within a time window | No heartbeat for 60 seconds |
Debouncing
To prevent flapping alerts, you can set a debounce window. The alert only fires after the condition remains true for the specified duration:
- 0s (default) — Fire immediately
- 10s — Condition must hold for 10 seconds
- 60s — Condition must hold for 1 minute
Cooldown
After an alert fires, the cooldown period prevents it from firing again for the specified duration. This avoids notification floods when a metric oscillates around a threshold.
Notification Channels
| Channel | Description |
|---|---|
| Sends to one or more email addresses | |
| Webhook | POST request to your URL with alert payload |
| Slack | Message to a Slack channel via incoming webhook |
| In-app | Notification in the Plexus dashboard |
Webhook Payload
When an alert fires, the webhook channel sends a POST request with:
{
"alert_id": "alt_xxxxx",
"name": "Motor Overheat Warning",
"source_id": "test-rig-01",
"metric": "cpu.temperature",
"value": 87.3,
"threshold": 85.0,
"condition": "above",
"triggered_at": "2026-02-27T14:30:00Z"
}Managing Alerts
From the Alerts page, you can:
- Enable / Disable — Toggle an alert without deleting it
- Edit — Change the condition, threshold, or channel
- Delete — Remove the alert permanently
- View history — See past triggers with timestamps and values
Alert States
| State | Meaning |
|---|---|
| OK | Condition is not met |
| Triggered | Condition is met, notification sent |
| Cooldown | Alert recently fired, waiting for cooldown to expire |
| Disabled | Alert is manually turned off |
| No data | Source has not sent data recently |
Next Steps
- Dashboards — Visualize your telemetry in real time
- Commands & Control — Send commands to devices from the dashboard