03 / ROUTING AND RECORDED DIAGNOSTICS · LESSON 12

Interpret recorded probe results

Keep timeouts, rejections and latency findings distinct in diagnostic reports.

18 min · learn at your pace

One unsuccessful attempt can mean several things

A recorded timeout means no usable response arrived within the collector's wait. It does not establish that a service is closed or a device is powered off. A refusal and a route-unreachable result provide different evidence and deserve different labels.

This lesson consumes a small validated probe export. It does not run ping, connect to an endpoint or scan ports. The result vocabulary is the collector contract: ok, timeout, refused or unreachable. Only ok records contain a latency measurement; the other results use a dash because no successful measurement exists.

Apply latency policy only to success

A successful probe with latency above the supplied maximum is slow. Equality remains reachable under this policy. Do not convert a missing latency into zero and report a timeout as fast, and do not apply latency thresholds before interpreting the result.

Retain the probe ID and device ID beside the classification. That makes it possible to trace a report back to the specific attempt. Repeated probes, transport differences and collection time matter in a real investigation, so a later capstone selects the latest evidence explicitly and records when an observation has become stale.

Try an example.sh
awk -F '\t' 'NR>1 {printf "%s recorded %s\n",$1,$3}' probes.tsv
YOUR TURN

Put it into practice.

probes.tsv contains validated probe_id<TAB>device_id<TAB>result<TAB>latency_ms rows. Result is ok, timeout, refused or unreachable; latency is a nonnegative integer only for ok, otherwise -. max_latency.txt contains a positive integer threshold. Print probe_id<TAB>device_id<TAB>assessment sorted by probe ID. For ok, use slow only when latency > threshold, otherwise reachable. Map timeout to unknown, refused to rejected and unreachable to route_error. Never treat timeout as proof of a closed port.

See an explained solution
One way to solve it.sh
export LC_ALL=C
read -r limit < max_latency.txt
printf 'probe_id\tdevice_id\tassessment\n'
awk -F '\t' -v limit="$limit" 'NR>1{
 if($3=="ok")s=($4>limit)?"slow":"reachable"
 else if($3=="timeout")s="unknown"
 else if($3=="refused")s="rejected"
 else s="route_error"
 printf "%s\t%s\t%s\n",$1,$2,s
}' probes.tsv | sort

The report derives a narrow conclusion from each recorded outcome. Missing latency is never converted into a successful measurement, and the explicit threshold boundary avoids inconsistent decisions at equality.