Playbook case study - Network outages
Case study: a customer fleet drops offline at once.
A cluster of remote gateways stops checking in and the customer wants to know whether to dispatch technicians. Use Dataplicity alerts, inventory, and last-known logs to prove whether this is device failure, regional connectivity, or account impact.
What the operator knows
A heartbeat alert fired for multiple devices at the same time.
CLI investigation walkthrough
Start from the alert, scope the cohort, then collect customer-safe evidence.
Operational conclusion
Dataplicity turns a noisy offline event into a specific next move.
- Scope outage by network cohort, customer, and region.
- Compare offline devices with backup connectivity cohorts.
- Use logs and events to separate provider issues from device faults.
- Attach evidence before updating customers.