VictoriaMetrics · Rate Limits

Victoriametrics Rate Limits

VictoriaMetrics is self-hosted (or VictoriaMetrics Cloud as a managed service); there is no managed REST quota in OSS. Operational caps are set via flags on each component (-search.maxConcurrentRequests, -search.maxQueryDuration, -insert.maxQueueDuration, -maxConcurrentInserts, -maxLabelsPerTimeseries, etc.). Enterprise multi-tenancy adds per-tenant cardinality / ingestion / query rate limits enforced at vminsert and vmselect.

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

It captures 5 rate-limit definitions, measuring concurrent_requests, ms, concurrent_inserts, active_series, and samples_per_second.

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

Tagged areas include Database, Time-Series, Monitoring, Open Source, and Prometheus.

5 Limits Throttle: 429
DatabaseTime-SeriesMonitoringOpen SourcePrometheusRate LimitingQuotasThrottling

Limits

Concurrent search requests (-search.maxConcurrentRequests) vmselect / single-node
concurrent_requests
see -search.maxConcurrentRequests flag
Default scales with CPU count; excess requests queue or 429.
Query duration cap (-search.maxQueryDuration) vmselect / single-node
ms
see -search.maxQueryDuration flag
Long-running queries are terminated.
Concurrent inserts (-maxConcurrentInserts) vminsert / single-node
concurrent_inserts
see -maxConcurrentInserts flag
Excess inserts queue or 429.
Active series per tenant (Enterprise) tenant
active_series
per-tenant Enterprise quota
Enforced via vmstorage flags in cluster Enterprise.
Ingestion rate per tenant (Enterprise) tenant
samples_per_second
per-tenant Enterprise quota
Configurable via -storage.maxIngestionRate or similar.

Policies

Backoff Strategy
Honor 429/503 with exponential backoff; vmagent buffers and retries on remote-write failures.
Capacity Planning
Right-size vminsert, vmselect and vmstorage per the cluster sizing guide.

Sources