Chronosphere Rate Limits
Chronosphere publishes throttling BEHAVIOUR in detail and throttling NUMBERS not at all. The limits are per-tenant and derived from the customer's contracted capacity, so the docs describe the meter, the trigger and the consequence precisely while the value of every limit lives in the contract and in an in-product dashboard. There are no published numeric thresholds to record and no rate-limit response headers at all.
Chronosphere Rate Limits is the machine-readable rate-limit profile for Chronosphere on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring PromQL selectors evaluated per second, READS = sum(DATAPOINTS_RETURNED_FOR_SERIES), minimum 60 data points per series, total compute resources available for log queries, and percentage of total available query resources.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and detail.
Tagged areas include AIOps, Observability, Rate Limiting, and Quotas.
limitremainingresetretryAfter
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.