The problem
Monitoring tools often show numbers in tables. A network is a graph, and a table hides which parts depend on which and where a problem will spread.
What I built
Dense network maps drawn with D3.js, plus an analysis of the data flow between nodes. You see the structure first and the detail second.
Design choices
The map shows structure first. Node size and link colour show load, so busy parts are easy to find. The map must pan and zoom smoothly when it is dense, or people stop using it.
Trade-offs
A dense graph can become a tangle. Grouping and filtering let a reader follow one path at a time.
What I learned
Leaving things out is the work.
A map with every node and every link shows everything and explains nothing.
The useful version drops most of the detail, keeps the structure and marks the busiest path. Grouping and filtering bring the detail back one question at a time.