Insights / Operations
A good incident briefing starts with simple evidence.
Community helps an operator summarize what is down, which important port changed, which underlay link is affected, and what read-only check was run next.
Briefing Layout
Build the incident note around four simple questions.
Scope
Which devices matter?
List the managed devices, discovered-only devices, and any affected topology links.
Signal
What changed?
Separate device unreachable, ICMP blocked but SNMP reachable, interface down, and recovery events.
Evidence
Why do we believe it?
Attach protocol evidence, timestamp, confidence, and source command or polling source.
Next Step
Keep the action read-only
For Community, the next step is diagnosis or reporting. Change execution belongs to Pro.