Columns
The column picker, not a scrollbar
Twelve columns do not fit in a panel, and a horizontal scroller is the worst way to hold a table: the columns you cannot see are the ones you forget you have. So the table opens on a set that fits, with the rest one click away in a picker beside its search box. Three things about it are deliberate. The menu is read off the column definitions, so the words in it are the words in the headers by construction. The tool name opts out — every other column is about it. What is hidden by default is what is already stated elsewhere on the same screen. Average response sits under the latency panel; schema bytes have a panel of their own. Never the outcomes, which are what the table was widened for — and not the sparkline either, which is the row’s own shape where the chart above it is the server’s. Your choice is stored as the difference from the defaults, per table. Storing “the hidden ones” would make a default-hidden column impossible to switch on; storing every column would pin you to whatever set existed the day you last opened the menu. The clients panel shares the same picker and the same outcome columns, so a row means the same thing on both.The status badge
Heavy payload is checked first, so a tool that is both heavy and struggling shows heavy payload — the larger, more concrete problem, and often the cause of the other.
These thresholds are the same constants the insight rules read. The table cannot say a tool is healthy while the panel directly beneath it says it is not.
Reading the table
Work down the calls column, not across it. The tool at the top is where a percentage point is worth the most. Three shapes worth recognising:- High calls, low first-call. The most valuable thing on the screen. See Improve first-call success.
- Low calls, large schema. Paying for something nobody uses. See Dead tools.
- Any calls, heavy payload. Every one of those calls is spending context. See Cut context cost.