Which paths are slow, which are erroring, and whether it is the same paths in both cases — from the response time your web server can already log.
| Card | What it shows |
|---|---|
| Headline | The overall latency picture for the current scope |
| Latency | The distribution over time |
| By path | Median, 95th and 99th percentile per path — the table that tells you what to fix |
| Status | A heatmap of status codes by hour |
All four carry the current request-kind and audience toggles, and changing either re-runs all four — they describe one scope and must not be allowed to disagree about it.
Apache’s microsecond directive, or nginx’s request time. Without it the field is absent rather than zero — because a zero would drag every percentile toward the floor — and this view has nothing to show. The recommended LogFormat includes it.
Everywhere else the panel queries the small sessions index. Response time is per request and lives on the hits index, so the percentiles cannot come from anywhere else. This view therefore aggregates over hits — but with facets only and no documents fetched, which respects the intent even where it does not follow the letter.
The verdict lives on the session document, not on each request, so filtering requests by verdict is not directly possible. The view handles this by counting how many matched requests carry a verdict at all, over the unfiltered domain, and telling you plainly when the filter cannot be applied — rather than drawing an empty chart and letting you believe it.
- Find the expensive endpoint a scraper has found. Cross-reference the slow paths here with the bot verdicts: an endpoint that is both your slowest and mostly non-human traffic is a cost you are paying for somebody else.
- Read the 99th percentile, not the median. A median that looks fine with a long tail is the shape of a page that is fast for cached content and slow for everything else.
- Use the status heatmap to spot a probe. A wall of not-found responses at one hour of the night is somebody walking a wordlist, and the session explorer will show you which session.