Rate Limiting
To provide a more stable throughput and fairness among different accounts in terms of resource consumption, ilert applies rate limiting to API and integration requests.
Last updated
Was this helpful?
To provide a more stable throughput and fairness among different accounts in terms of resource consumption, ilert applies rate limiting to API and integration requests.
Last updated
Was this helpful?
If a request exceeds the defined rate limit, the request is rejected with the HTTP status code 429 Too many requests.
The following rate limits apply:
API (IP)
700 (can be increased)
1 Minute
UI (IP)
250
1 Minute
Integration Key (Alert source)
50 (can be increased)
1 Minute
Integration Key (Deployment pipeline)
10 (can be increased)
1 Minute
API Key (User generated)
120 (can be increased)
1 Minute
Integration Key (Metric series)
12 calls or 240 points (can be increased)
1 Minute
Integration Key (Heartbeat)
5
1 Minute
Exceeding a limit will cause a client to be rejected with 429 responses until a new window starts. There are no other consequences.
Clients may retry their requests on 429 responses with a backoff timeout, 10-30 seconds are suggested.
In case of integration key limits for alert sources, we will show a warning message on alert sources (and their related alerts) which limits exceeded. This message will disappear automatically after 48 hours.