Follow a network symptom to the affected circuit
Use the local LibreQoS console for live topology, queues, and flow evidence. Add Insight for history, reports, alerts, and centralized views.
Conceptual example. Parent groups and circuit mapping come from your network configuration.
- 01Network symptom
Compare sites and nodes
- 02Affected branch
Check capacity and quality
- 03Circuit
Inspect queues and RTT
- 04Flow / ASN context
Choose the next investigation
Locate the affected branch
Use the local Network Tree to compare parent capacity and child behavior, then narrow the incident to a circuit.
- Live hierarchy and throughput
- RTT and retransmit context
- Queue limits beside observed behavior
Inspect the circuit before changing it
Review queues, active flows, and Quality of Outcome (QoO), an estimate based on latency and loss, alongside the underlying measurements.
- Per-circuit queue evidence
- Flow and destination context
- Signals to correlate with access and subscriber equipment
Carry the timeline into Insight
Insight adds history from 15 minutes to one year, circuit reports, ASN analysis, and views across one or many shapers.
- Check when the pattern changed
- Compare sites over the same interval
- Build an evidence-based escalation
Circuit investigation
Put the subscriber symptom beside the queue evidence
Review the circuit parent and plan limits, then compare throughput, retransmits, and RTT in Queue Dynamics. Use Insight to revisit historical intervals across one or many shapers.
Walkthrough
See how operators move from network symptom to subscriber evidence
These views show ASN analysis, map context, and circuit-level drill-down in one investigation workflow.
Plan your pilot
Put the workflow to work
Validate LibreQoS on your network
Start with a limited pilot, compare the same load conditions, and confirm the affected branch and circuit behavior before expanding.