Dynatrace · Rate Limits
Dynatrace Rate Limits
Dynatrace API rate limits are enforced per environment and per access token. The platform does not publish a single rate-limit page; limits vary by API (Environment, Configuration, Account Management, OpenPipeline, Davis AI, DQL/Grail Query). Throttled callers receive HTTP 429 with Retry-After. Quota for ingest is governed by your subscription (DDU/DPS/host quota), not by raw HTTP request rate.
6 Limits
Throttle: 429
Quota: 429
Rate LimitingObservabilityAPM
Limits
Environment API (per-tenant) tenant
see Dynatrace API reference per endpoint
Configuration API (per-tenant) tenant
see Configuration API reference
Account Management API account
see Account Management API reference
Metrics ingest tenant
governed by DDU/DPS quota
Throughput governed by your subscription consumption units rather than HTTP rate.
Logs ingest tenant
governed by Log Management entitlement
DQL/Grail query tenant
see Grail concurrency guidance
Policies
Retry on 429
Honor the Retry-After header on 429 responses; back off exponentially with jitter.
Token-scope limits
API tokens carry permission scopes that may impose tighter limits than the tenant default; refresh or rotate tokens via the Access Tokens API.
Subscription-driven quotas
Ingest throughput (metrics, logs, traces) is bounded by Davis Data Units (DDU), Dynatrace Platform Subscription (DPS) units, or host capacity, not raw HTTP rate.
Sandbox vs production
Sandbox environments share lower limits than production tenants; do not load-test against sandbox.