Get Query Latency
Latency percentiles and a histogram for a window of your stored queries.
Unlike GET /v2/queries, which pages through individual records, this summarises the whole filtered population in one bounded response: counts, exact p50/p95/p99, explicit histogram edges, and the same bins per collection so their shapes can be compared.
Two numbers are reported separately on purpose. counts.measured are the
queries with a recorded processing time; counts.missing are matching
queries without one, which are left out of the percentiles rather than
counted as zero milliseconds. coverage says how much of the population
recorded each filterable setting, because older queries predate some of
them and answer unknown.
Windows are capped at 90 days. Use GET /v2/queries to drill into individual queries.
Query parameters
Start of the window, inclusive. ISO-8601 date or timestamp (UTC when no offset is given).
v3, v2, or unknown for queries that recorded no version.
The recorded rerank setting: on, off, or unknown. A setting of on does not mean reranking ran.
keyword, semantic, hybrid, or unknown, derived from the recorded semantic ratio.
true, false, or unknown for queries that recorded no filter setting.
Histogram resolution (4-64; default 16). Edges are returned explicitly.
Response
Which queries the metric covers. Completed, non-evaluation queries: a failed query records no usage row, and evaluation units are excluded.
Per filter, the share of matching queries that recorded that dimension (0.0-1.0). A low value means most of the population answers unknown.
What is being measured: server-side query processing time, not end-to-end client latency.