Problem
People need to find unusual machines in a large fleet without reading hundreds of table rows.
Solution
Show each host as a cell colored by a selected metric. Label the metric and scale, and provide another way to identify important states besides color.
Group hosts by meaningful attributes such as location or type. Keep those group boundaries clear so people can distinguish a single unusual host from a wider problem.
Let people filter the fleet and open a host’s details. At larger sizes, summarize groups rather than shrinking cells until they become unreadable.
Use when
A large fleet contains comparable machines and people need to locate current exceptions.
Don’t use when
There are twelve hosts, or the machines are so heterogeneous that one metric doesn’t mean the same thing across them. Also a poor fit for anything you need history on: the map is emphatically now.
Trade-offs
One selected metric can hide problems in another. The layout may look geographic even when it is only grouped. Small cells and heavy dependence on color make exact comparison difficult.
Checklist
- What metric fills the cell, and does it mean the same thing on every host here?
- Is the grouping visible and labelled, or is the arrangement effectively random to the viewer?
- Can the viewer group by more than one dimension, and does nesting read clearly?
- Does the colour ramp encode magnitude or state, and is the difference obvious?
- What happens at the fleet size this team actually runs?
- Can a cell be too small to read, and what does the view do about it?
- Does clicking a cell go somewhere scoped to that host?
- Is a host with no data distinguishable from a healthy one?
- Would a colourblind viewer find the same outliers?
- Is there any way to see whether this pattern of colour is new or has been like this all week?
Compare
Datadog owns this pattern: hexagon tiling, a default CPU fill from green to orange, arbitrary Fill by metrics, size by metric, and nested grouping over tags with boolean filtering. Netdata answers the same question with a node list carrying live per-second charts, trading the instant spatial scan for the ability to see whether a host has been like this for ten minutes or ten seconds. Grafana has no first-class equivalent, so teams build it from a stat panel grid or a geomap, which works and puts the burden of layout and grouping on whoever assembles the dashboard. Honeycomb rejects the framing outright, on the argument that the interesting dimension is rarely “host” and that pre-choosing it is what makes an unknown-unknown invisible.
Related
Service map shows relationships between services. Semantic status color defines state meanings. Ranked list offers an ordered alternative.
Drill-down opens host details. Grayscale with alerts keeps exceptions distinct from routine activity.