Sign in
queries

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.

get/v2/queries/latency

Query parameters

fromstring nullable

Start of the window, inclusive. ISO-8601 date or timestamp (UTC when no offset is given).

tostring nullable

End of the window, exclusive.

collectionstring nullable

Only queries against this collection.

api_versionstring nullable

v3, v2, or unknown for queries that recorded no version.

rerankstring nullable

The recorded rerank setting: on, off, or unknown. A setting of on does not mean reranking ran.

search_modestring nullable

keyword, semantic, hybrid, or unknown, derived from the recorded semantic ratio.

has_filterstring nullable

true, false, or unknown for queries that recorded no filter setting.

binsinteger nullable

Histogram resolution (4-64; default 16). Edges are returned explicitly.

refreshboolean

Recompute instead of serving a briefly cached result.

Response

Successful Response

coverageobject

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.

generated_atstring required

When these numbers were computed. A cached response keeps its original value.

metric'query_processing_time'

What is being measured: server-side query processing time, not end-to-end client latency.

metric_versionstring
percentile_method'exact'

Percentiles come from the measurements themselves, not an approximate sketch.

populationstring required

Which queries the metric covers. Completed, non-evaluation queries: a failed query records no usage row, and evaluation units are excluded.

unit'ms'

Changes

Changed in 2 of the 13 revisions of this API.4120

  • 61a9364ad0424119See the full diff
    • ▲

      the response's body type changed from no type to object for status

      response-body-type-changed

    • ▲

      the response's body type changed from no type to object for status

      response-body-type-changed

    • ▲

      the response's body type changed from no type to object for status

      response-body-type-changed

    • ▲

      the response's body type changed from no type to object for status

      response-body-type-changed

    • ●

      removed the optional property from the response with the status

      response-optional-property-removed

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    This revision also has 10 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 6ed36830de711See the full diff
    • ○

      endpoint added

      endpoint-added

    This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog