/m/:id/tools/:name is one tool, with the same metrics as the overview scoped down to it.
What is on the page
The outcome breakdown and latency distribution render from the same components and the same shapes as the overview, so the two screens cannot disagree about what “ok” counts.
Calls per day carries three series
Calls,ok and empties per day. Reading them together is usually how a problem gets located in time: an empties line that lifts on a particular day points at a deploy, a data change, or an upstream that started returning nothing.
Gap-filled, so a quiet day plots as zero.
Follows
Up to ten tool pairs where this tool is either side. Nightly, so it lags by a day. Pairs are the fastest way to understand when a tool is used rather than how often. A tool that always follows one particular search is part of that search’s job, whatever its description says.Registered but never called
A tool that appears in the startup payload but has no recorded calls still has a page. Every figure reads zero,never_called is set, and the schema size is the one real number on it — which is the point. See Dead tools.
A name that is neither registered nor recorded returns 404.
The name is what the client sent
The recordedtool_name is request.params.name — what the client actually asked for, not what you meant to register. If a tool is missing from the list but you know it runs, check the name matches exactly.