Return queue history for backlog and throughput trends.

The UI leads with time-to-drain rather than depth. That is a rate, and a rate needs history — which the first draft of this spec had no way to serve. Backed by incrementally maintained counters, never by a queue-depth scan.

GET /queues/{queue}/history

Error

A valid request URL is required to generate request examples

200

[
  {
    "at_ms": 123,
    "arrived": 123,
    "completed": 123,
    "failed": 123,
    "depth": 123,
    "admission_rejections": {}
  }
]

Path Parameters

queue · string · required

Query Parameters

since_ms · integer

bucket_ms · integer · default: 60000

Response

200 - application/json

Queue history buckets.

at_ms · integer

arrived · integer

completed · integer

failed · integer

depth · integer

admission_rejections · object

Rejections grouped by policy. Without this, a misconfigured limit looks exactly like a slow worker.

Show child attributes