Triage network connectivity issues
Establish affected users, locations, services, timing, and safe diagnostic evidence before routing or changing network controls, while minimizing collection from member devices.
| Field | Value |
|---|---|
| Business area | access-network-printing |
| Primary role | it-security-administrator |
| Frequency | continuous |
| Privacy sensitivity | high |
| Security sensitivity | high |
| Compliance review | not normally required |
Trigger and handoff
Trigger: A user or monitor reports unavailable, unstable, slow, or unsafe connectivity.
Inputs
- User-provided symptoms and consent
- Network health context
- Recent approved changes
Outputs
- Severity and scope assessment
- Safe workaround or assigned investigation
- User update
Current manual methods
- Restart advice
- Speed test screenshot
- Direct admin troubleshooting
Human judgment and approvals
-
Distinguish device
-
account
-
radio
-
upstream
-
and security signals
-
Choose diagnostics proportionate to impact
-
Approval: Network owner approves configuration changes
-
Approval: isolation
-
Approval: and intrusive diagnostics
Failure modes
- One device issue is declared an outage
- Excessive device data is collected without purpose
Success metrics
- Issues are scoped correctly before change
- Users receive timely status and a safe next step