M16.3 Full API analysis: breakdowns, consumers, comparisons #66

Part of #63. Needs M16.1.

yuva-api

• Breakdowns and filters: any combination of the core dimensions (route, method, status, status class, API version, environment, service, source server or app, platform) from every tier, plus at most one extra dimension (consumer, country, app version) from hours and days; 422 dimension_combination otherwise.
• Metrics p75, p90, max_duration, apdex (threshold per property and per route), request_bytes, response_bytes, response_size_p50, response_size_p95; comparisons with the previous period and a year earlier; throughput per minute; slowest and most failing routes; new routes and silent routes.
• Consumers: requests, errors and latency per consumer; top consumers per route; the latency heatmap from sketch buckets.
• Deploy markers: a new release per service and environment writes a deploy annotation with a time (at), read-only like Yuva's other annotations.

yuva-panel

• Filters and breakdowns on the overview and route pages, a consumers view, period comparison, deploy markers, the latency heatmap, a clear message when a combination needs two extra dimensions. en and tr.

yuva-docs

• What each number means, how percentiles are computed (1.1% bucket width), what sampling does to the numbers, which combinations are answered; en, tr, de.

Done when

Every view filters and breaks down by each core dimension and each pairing with one extra dimension, with numbers that match a hand-counted fixture (percentiles within 1.1%); comparisons, Apdex and new and silent routes match the fixture too.