FaultOne - example reports
Nine reports this tool produced, as the page --export writes.
Each one is a different fault, and the headline is the tool's own answer to
which fault to fix first - not a list of everything that looked wrong.
Open one and read the three boxes: the way in, this box, the way out.
These are built from the test suite's fixtures, never from a live
run. A report is a map of the network it was taken on, so a demo taken
from a real machine would publish the addressing of whoever made it. Every page
here is regenerated and re-checked on each release: a page whose verdict stops
naming the fault in its filename fails the build rather than shipping.
Start with these
The loss is on what talks to this box, not on what it talks to
in FAILthis box PASSout PASS
inbound loss
The loss is on what this box talks to, not on what talks to it
in PASSthis box PASSout FAIL
outbound loss
This box is running out of ports to open connections from
in PASSthis box WARNout WARN
port exhaustion
No outbound internet from here, while clients are connected inbound
in PASSthis box WARNout WARN
egress blocked
A service address is configured here and nothing is accepting on it
in WARNthis box PASSout PASS
service address
Then, if you want the rest
This box is sending to its backends and nothing is coming back
in PASSthis box PASSout FAIL
return stalled
The loss is on what this box talks to, not on what talks to it
in PASSthis box PASSout FAIL
losing and quiet
The delay to the backend is queue, not distance
in PASSthis box PASSout WARN
queue not here
Clients are reaching this box over TCP because datagrams are not getting through
in WARNthis box WARNout PASS
two planes