Define the symptom and measurement
Record the source, destination, application, time interval and test method. Distinguish transaction time from network round-trip time, and distinguish an endpoint failure from a missing response at an intermediate hop. Different measurements can answer different questions.
Document the expected path and a representative healthy comparison. Network Context provides the service and routing assumptions; Troubleshooting Context defines how your team interprets counters, intervals and monitoring observations.
Build a time-aligned evidence set
Use comparable observation windows before drawing correlations. Keep cumulative counters separate from changes measured during the incident.
| Evidence | Useful comparison |
|---|---|
| Application transaction | Affected interval versus accepted service baseline. |
| Endpoint probe | Same source, target and test method over comparable intervals. |
| Interface counters | Counter changes and collection times, not only historical totals. |
| Path observations | Expected path versus observed changes. |
| Monitoring and device events | Whether events coincide with the reported symptom. |
Illustrative example: loss appears only during a busy period
A branch reports slow transactions at a recurring time. The workflow gathers the configured observations during an affected interval and compares a healthy interval. It preserves test conditions and aligns relevant interface and monitoring evidence.
If the evidence suggests congestion, the report identifies the observations supporting that hypothesis and any missing measurements. It does not conclude that historical error totals or one unanswered probe prove congestion or the service root cause.
Use NetPrompt for evidence collection and explanation
Configure the checks your platforms and monitoring tools can provide. Scheduled or on-demand workflows can organize observations within their validated execution scope; determine polling intervals and load with the operational owner.
This use case does not claim a built-in packet capture engine or automatic continuous path monitoring. Where packet capture or specialist telemetry is required, use an approved tool and a validated integration or reviewed evidence handoff. Start with the smallest evidence set that can test the hypothesis.
Review the diagnosis before remediation
The useful output states the measurement, interval, findings, competing explanations and next action. Capacity changes, policy adjustments or path changes require their own impact assessment and authorization.
Validate recovery using the same representative service test and relevant observation period. During evaluation, include healthy traffic, a known fault and incomplete telemetry. Assess whether the workflow avoids overclaiming certainty and reduces the manual effort of assembling evidence.
Common questions
- Does a missing traceroute response prove packet loss for application traffic?
- No. Intermediate devices may handle diagnostic responses differently from forwarded traffic. Correlate endpoint and application evidence before concluding service loss.
- Can old interface errors prove the current incident?
- Not alone. Record counter changes over the relevant interval and compare them with other observations.
- Does NetPrompt provide packet capture for every device?
- This page describes a configurable evidence workflow. Validate any capture or telemetry capability and integration separately.
Continue exploring
Further technical reading
External references explain general practices; they are not endorsements of NetPrompt AI.