Individual devices and fleet groups
Watch a device or a tagged cohort. Alert on offline counts or percentages, with trigger and recovery thresholds appropriate to that group.
Know what is affected. Carry the response through to recovery.
Monitor devices, fleet groups and services around the same equipment records. Turn matching monitor conditions into alerts and incidents, bring the right responders in, and keep investigation, customer communication and recovery evidence together.
- Watch individual devices, fleet offline counts and percentages, heartbeats, service endpoints and user-impact signals.
- Fleet monitors, alerts, incident handling and on-call escalation belong to the Business+ operating suite; fleet monitor access also follows the release channel.
- Fleet SLOs provide tag-scoped customer availability evidence and require Enterprise.
Monitor the equipment and the service it delivers.
Choose signals around the failure your team needs to notice, not just whether Linux is still running.
Heartbeats and service endpoints
Detect missed check-ins from a scheduled task or service, and monitor endpoint availability. Device presence and application health answer different questions.
User impact
Monitor a customer-facing journey or service signal alongside the devices that support it. A connected device can still be delivering a broken customer experience.
Pulse and connection quality
Compare similar devices for unexpected drift with Pulse. Inspect available connection-quality history and ISP performance when the pattern points to connectivity.
Explore this capabilityTurn a signal into an actionable response.
Configure the scope, conditions and timing before putting the rule into service.
Define the affected cohort
Use maintained device tags for a customer, site, device class or connectivity provider. Verify that the group contains the equipment you intend to monitor.
Combine conditions
Alert rules can require all selected monitor conditions to match. Trigger windows, recovery conditions and cooldown settings help make the response deliberate rather than reacting to every brief fluctuation.
Choose the response route
Configure notification channels and an escalation path for the incident. Exercise a representative failure and recovery so the team knows what arrives and who must act.
Explore this capabilityOne ISP goes offline. The rest of the fleet stays alive.
Illustrative workflow: gateways using one provider stop checking in together while devices on other providers remain online. This is evidence of a shared dependency to investigate, not proof of the root cause.
Detect the group failure
Maintain an ISP-tagged cohort and a fleet offline monitor. When its configured threshold and trigger window are met, use an alert rule to raise the incident.
Compare affected and healthy devices
Check last-seen times, devices outside the cohort, and available ISP connection-quality history. Inspect reporting coverage so missing samples are not interpreted as healthy devices.
Investigate and communicate
Review collected logs and recent changes, assign the response and record the evidence. Escalate to the appropriate team and publish a customer-safe status update when needed.
Verify the whole group recovers
Track fresh check-ins and the configured recovery condition. Investigate remaining exceptions and update the incident; one recovered gateway is not evidence that the entire cohort is healthy.
Explore this capabilityGive the next responder the same context.
An incident carries the work from the first signal to the follow-up.
Acknowledge and escalate
Manage open, acknowledged and resolved incidents, with on-call schedules and escalation paths. Bring device and severity context into notifications; mobile incident workflows support acknowledgement.
Explore this capabilityInvestigate with evidence
Keep incident notes and device context together. Search collected logs while equipment is offline; use a terminal or Network Connector once the target device is online.
Explore this capabilityUse AI for the next useful check
Use the fleet AI workspace to compare devices and prepare investigation steps, or the terminal copilot for a focused device. Review scope and commands before changing equipment.
Carry out and track the work
Use fleet jobs or scheduled tasks where a repeated operating action is appropriate. Keep remediation and follow-up linked to the incident and device evidence.
Explore this capabilityExplain the impact to customers and service owners.
Live monitoring, customer communication and an availability commitment are related but distinct jobs.
Status pages
Publish customer-facing availability and incident updates using your monitor and incident context. Choose what to publish without exposing the engineering workspace.
Explore this capabilityDashboards and wallboards
Put fleet health and service signals into read-only dashboards for customers or the team handling the response.
Explore this capabilityFleet SLOs and uptime evidence
Define a customer agreement around a tag-scoped fleet, inspect historical availability and retain calculation evidence. Fleet SLOs require Enterprise; monitoring alone is not a contractual uptime guarantee.
Keep security evidence beside the operating evidence.
Access policy and security findings matter when deciding what changed and who reached the equipment.
Review detections and access history
Investigate suspicious account activity alongside sign-ins, remote sessions and administrative changes. Security detections can notify a configured webhook; review their scope before choosing the response.
Explore this capabilityControl the investigation
Use team permissions and connector device-and-port grants for access. Record the operator action and result, then review whether any temporary access should remain.
Explore this capabilityEvaluate a complete failure and recovery.
Start with the signals and response your team actually needs. Available monitors, capacity and channels follow your plan and configuration.
Device diagnosis on paid plans
Single-device monitoring, Pulse and collected logs support focused investigation. Pulse needs comparable devices and time for evidence to accumulate.
Business+ response workflow
Fleet monitors, alerts and alert rules, incident management and on-call escalation form the operating suite. Fleet monitors also require the appropriate release-channel access. Test a failure, notification, acknowledgement and recovery on a representative cohort.
Enterprise availability evidence
Evaluate fleet SLOs using a defined customer scope and evidence window. Confirm which devices and missing observations contribute to the calculation.
Explore this capabilityProve the response to one real operating problem.
Choose a cohort and monitor condition, configure the responders, then exercise both the failure and the recovery.