Sleuth · Rate Limits

Sleuth Rate Limits

Sleuth's registration API applies endpoint-specific throttling. The custom metric impact registration endpoint is documented as accepting at most one value every 120 seconds per impact source, and rejects timestamps that predate the impact source's creation (no backfilling). Other registration endpoints (deploy, manual change, incident impact) and the GraphQL surface do not publish explicit numeric limits; verify any account-level limits with Sleuth during reconciliation.

Sleuth Rate Limits is the machine-readable rate-limit profile for Sleuth on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests and timestamp.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include DORA, DevOps, Deployment Tracking, Engineering Metrics, and Continuous Delivery.

5 Limits Throttle: 429
DORADevOpsDeployment TrackingEngineering MetricsContinuous DeliveryRate LimitingQuotasThrottling

Limits

Custom Metric Impact Cadence impact_source
requests
1 per 120 seconds
At most one metric value may be registered every 120 seconds per impact source.
Impact Backfill Restriction impact_source
timestamp
no dates before impact source creation
Registered dates may not predate the creation of the impact source.
Deploy Registration account
requests
see provider documentation
No explicit numeric limit published for deploy registration.
Manual Change Registration account
requests
see provider documentation
No explicit numeric limit published for manual change registration.
GraphQL API account
requests
see provider documentation
GraphQL surface is under active development; limits not published.

Policies

Per-Source Throttle
Custom metric impact values are capped to one every 120 seconds per source.
Backoff Strategy
Clients should honor 429 responses and implement exponential backoff with jitter.

Sources