Forum01
Notice a sustained group condition.
Configure meaningful device groups, failure thresholds and persistence windows.
Know when a whole group of customers is affected.
Notice a shared failure. Coordinate the response. Follow recovery.
Configured fleet monitors · Northstar demo fleet
One offline unit—or a shared failure?
02
Bring the evidence and responders together.
Compare healthy equipment, inspect collected history and coordinate the incident.
03
Follow recovery across the group.
Check fresh device and service evidence. Keep unresolved units visible.
Fleet monitoring and incidents require Business+. Compare carrier and service evidence before assigning a cause.
Setup and technical guides ↓Setup and technical guides
Choose the setup question or guide you need.
Detailed workflow and operating states
Illustrative operating sequence. People choose the scope and intervention; configured collection, rules and device behaviour supply the evidence.
Step 1 · Maintain a meaningful cohort
For example, group gateways that use T-Mobile. Verify the active carrier on each device before recording it in tags or groups. T-Mobile is an example, with no implied partnership.
Step 2 · Detect a material sustained condition
Configure the affected proportion, persistence window and recovery criteria for a fleet monitor. Account for reporting coverage and missing observations; a quiet device and a measured service failure are different evidence.
Step 3 · Compare, investigate and coordinate
Responders compare last-seen times, connection-quality history and healthy cohorts. The configured rule raises an incident and notification or on-call escalation. Review collected logs and security evidence; approve customer communication rather than broadcasting raw engineering information.
Step 4 · Follow the whole group back to service
Check fresh check-ins and application/service evidence against the configured recovery condition. Keep remaining exceptions visible and record the outcome before closing the incident. Live access requires the affected agent to reconnect.
What you do not have to reconstruct between tools
Group identity, monitor observations, incident notes and affected customer/site context support the handover between responders. Choose the relevant cohort explicitly. Correlation identifies a shared dependency to investigate; it does not prove T-Mobile caused the failure.
Keep the responsibility clear
Previously collected history can support an offline investigation; missing observations must stay visible. Carrier causation and customer service restoration require further evidence.
What would we need to change?
Configuration, product engineering and subscription eligibility are different requirements.
Enable and configure
Connect the fleet, maintain accurate membership, enable signals and configure thresholds, persistence, notification recipients and escalation. Test a synthetic failure and recovery with a limited demo group before relying on the policy.
What you keep
Keep your equipment, chosen Linux, application and retained business tools. Provider contacts and external service-desk integration remain your responsibility where needed.
Plan and readiness
The fleet-monitoring and incident suite follows Business+ entitlement and current release access. Enterprise adds fleet SLO capabilities. Plan eligibility does not create your groups, alert policy or on-call rota.
Read the guide → →
The tools underneath the job
Use the exact implementation guides to check the supported contract and limits.
Fleet monitoring
Configuration and implementation requirements.
Read the guide → →Incidents and on-call
Configuration and implementation requirements.
Read the guide → →Connection evidence and remote access
Configuration and implementation requirements.
Read the guide → →
Bring a specialist into the work
Ask for help where evidence or an integration decision is unclear. Use the context and permissions available to that conversation.
Hardware, product and operations help
Equidna helps connect supplied hardware evidence to the software path; Nutria helps plan the customer job; Pingüino helps investigate authorised operational evidence. Shared-room help remains read-only. 24/7 AI assistance has plan and usage conditions.
Read the guide → →
Choose one useful result to prove.
Use the reference to build your own test. Validate the hardware, integration and operating process on your product.
Exercise the Northstar incident reference
Review the procedure and qualify the parts your product requires.
Read the guide → →Check adoption requirements
Start with the product you have, then choose independent optional paths.
Read the guide → →
Start with this job.
Connect the fleet, maintain accurate membership, enable signals and configure thresholds, persistence, notification recipients and escalation. Test a synthetic failure and recovery with a limited demo group before relying on the policy.