Chronosphere · Rate Limits

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, conforming to the API Commons Rate Limits specification.

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.

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.

5 Limits Throttle: 429
AIOpsObservabilityRate LimitingQuotas

Limits

Selectors per second per-tenant
PromQL selectors evaluated per second
contract-derived
Data reads per second per-tenant
READS = sum(DATAPOINTS_RETURNED_FOR_SERIES), minimum 60 data points per series
contract-derived
Log global query limit per-tenant
total compute resources available for log queries
contract-derived
Log user query limit per-user
percentage of total available query resources
contract-derived
Log API query limit per-api-caller
percentage of total available query resources
contract-derived

Policies

Grace window
Neither query limit begins dropping until it has been exceeded for 10 consecutive minutes.
Drop, not queue (metrics queries)
Metrics query overload sheds an indiscriminate subset of queries. A client cannot assume its own request will survive, and cannot tell a dropped query from a failed one without the 429.
Queue, not drop (log queries)
Log queries exceeding the global limit are queued and run when resources free up.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/chronosphere-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.