Know when a device needs attention.

Set conditions for device health and availability, then route notifications to the people responsible. Check the affected devices and evidence before deciding what to do.

Dataplicity alerts showing active connectivity events across customer sites
  • Threshold, heartbeat, and expression rules.
  • Routing and on-call escalation in the same UI.
  • Alerts stay tied to device identity.

Alert rules

Define alert policies once and reuse them across cohorts.

Metric thresholds

Trigger alerts on CPU, memory, or custom metrics.

Offline detection

Alert when devices stop checking in.

Fleet ratios

Alert on fleet-wide ratios or availability.

Routing and incidents

Route alerts into incident workflows.

On-call escalation

Route alerts to the correct rota.

Incident management

Attach notes and resolution steps.

Alert history

Track alert history against the device.

Follow the condition through to recovery.

An alert is the start of the operating workflow. Keep the affected devices, response and evidence together.

Monitor the right group

Watch device and fleet conditions, compare ISP and site cohorts, and check which services are affected.

Explore this path

Bring in responders

Use the Business+ incident and on-call suite for acknowledgement, escalation and investigation notes.

Explore this path

Explain and verify the result

Publish appropriate customer updates, verify recovery across the affected group, and retain availability evidence. Fleet SLOs require Enterprise.

Explore this path