Dynatrace · Rate Limits

Dynatrace Rate Limits

Dynatrace throttles the API by CAPACITY, not by a published request-per-second quota. Every environment has a limited thread pool with a queue; you hit the limit when both the pool and its queue are full, or when a request times out waiting in the queue after 10 seconds. Exhaustion returns HTTP 429. What Dynatrace DOES publish precisely is payload ceilings per API, and a charging model in which reads are free on fair use while defining and pushing custom metrics is billed per metric per month.

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

It captures 8 rate-limit definitions, measuring concurrent_requests, bytes, and custom_metrics_per_month.

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

Tagged areas include Rate Limiting, Observability, and APM.

8 Limits Throttle: 429
Rate LimitingObservabilityAPM

Limits

Environment request throttling (thread pool + queue) environment
concurrent_requests · instantaneous
capacity-based — not a published numeric quota
Deliberately designed so many cheap requests pass while expensive ones are the ones that queue. Cost per request, not request count, is what exhausts the limit.
Default payload size request
bytes · request
1048576
Log Monitoring API payload request
bytes · request
10485760
Ingestion API payload (upper tier) request
bytes · request
8388608
Ingestion endpoints cap at 8 MB, 4 MB or 2 MB depending on the endpoint.
Extensions API upload request
bytes · request
52428800
Plugins API upload request
bytes · request
52428800
Mobile Symbolication API upload request
bytes · request
104857600
Custom metric charging environment
custom_metrics_per_month · month
billed per metric per month — governed by DPS or the classic DDU model, not by HTTP rate
Read access to the Dynatrace API is free of charge on a fair-use model. Defining and pushing NEW custom metrics is charged.

Policies

Back off blindly on 429
There is no Retry-After header to honour. Retry with exponential backoff and jitter, and widen the interval rather than the batch — the throttle is capacity-based, so a smaller, cheaper request is more likely to pass than a delayed large one.
Split expensive queries
Because the queue admits many cheap requests and few expensive ones, narrowing a selector or shortening a query window is a more effective remedy than reducing request frequency.
Retries are not safe on ingest
Dynatrace publishes no idempotency key. A retry after a 429 on ingestLogs, ingestEvent or ingestCustomMetrics duplicates the datapoint. See conventions/dynatrace-conventions.yml.
Subscription-driven quotas are separate from HTTP throttling
Ingest volume is bounded by the Dynatrace Platform Subscription or the classic DDU/host entitlement. That is a licence limit, not an HTTP rate limit, and it does not surface as 429.

Sources

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/dynatrace-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.