Enforce rate limits on webhook executions for customers per plan
Release notes
Introduced in %15.2 for GitLab.com users, rate limits will be enforced to protect the performance and availability of the GitLab application (and in return it protects performance for all tenants). Limits are applied per plan and namespace, and are based on the number of seats in your subscription.
Rate limits
The number of times a webhook can be called per minute, per top-level namespace. The limit varies depending on your plan and the number of seats in your subscription.
| Plan | Default for GitLab.com |
|---|---|
| Free | 500 |
| Premium |
99 seats or fewer: 1,600100-399 seats: 2,800400 seats or more: 4,000
|
| Ultimate and open source |
999 seats or fewer: 6,0001,000-4,999 seats: 9,0005,000 seats or more: 13,000
|
Learn more by visiting our documentation on webhook rate limits.
Description
After we've added soft limits with logging in #337228 (closed), this issue will follow up to enforce the limits. Below are the required steps:
- Reviewing the logs and discussing
- Implementing the hard limit
- Working out what to do with the single Premium customer who is the outlier #337228 (comment 992723695) (either working with them to change or else perhaps making them exempt at least in the medium term)
See discussion in https://gitlab.com/gitlab-org/ecosystem-stage/team-tasks/-/issues/146#note_993254234.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.