...
To visualize the traceroute information, we define the severity of an anomaly in traceroute. Based on that severity, we decide which anomaly should be presented, e.g. If one traceroute has any missing hop plus a destination hop not responding. In our case, destination hop not responding is of high severity than any other missing hop. So we prefer to show destination hop not responding with a specified character instead of any other missing hop. The color represent severity and the character symbol represent anomaly.
Detail traceroute information is provided with the help of pop-ups. Pop-up over traceroute symbol provides the actual traceroute text with anomolies colored. E.g. checksum error is shown as orange and change in traceroute from the previous one is shown as red (intensity of redness specifies the severity of change).
Severity | Color |
|---|---|
0 | Green |
1-3 | Orange |
4-5 | Red |
Symbol | Description |
|---|---|
X | Host Unknown |
U | No Output |
u | The output is not parsable |
N | The last hop is not responding |
A | The Autonomous System change occured in traceroute |
a | The Subnet Change occured in tracerotue |
-- | Stutter |
! | Annotation |
o | Some hop(s) are not responding. |
~ | Checksum error |