Rate limits consumtion summary
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
In this support ticket (internal link) the customer had difficulties to spot a rogue services hitting the api for gitlab.com in the background, and making it reach the rate limits.
Proposal
That would be nice, for the admin of a namespace, to be able to have a break down of each rate limit consumed so that would be easier to investigate: which IP is hitting the rate limits, which user, which path, etc.
Intended users
Any gitlab.com users
Feature Usage Metrics
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.