Vetrix Docs

Rate limits

The Rate limits page sets how many requests each group of users may make against the instance, for every category of request, and lets you change those budgets without a deployment. It shows a summary of recent throttling, a grid of budgets by group and category, and an editor for any single cell.

This page appears only if your administrator account has the corresponding permission.

Where to find it

Open your avatar menu in the top navigation bar and select Admin panel, or go to gitvetrix.com/admin directly. In the admin sidebar, under Access & Security, select Rate limits.

URL pattern: gitvetrix.com/admin/rate-limits

Read the summary cards

Three cards across the top of the page summarize recent activity:

  • Requests throttled 24 h — how many requests were throttled in the last 24 hours.
  • Unique throttled users 24 h — how many distinct users were throttled in that window. A trailing + means the figure is sampled from a large number of recent events.
  • Active overrides — how many per-repository and per-application overrides are currently in effect.

Read the budget grid

Below the summary, the System groups table lists the three built-in tiers as rows — anonymous, general, and admin — with one column per request category: api.read, api.write, api.expensive, git.read, git.write, registry, and beacon. If your instance defines its own groups, a second Custom groups table appears beneath the first.

Each cell shows the budget for that group and category in the form requests / window s · bburst — for example, 600 / 60s · b60 means 600 requests per 60-second window with a burst allowance of 60. A cell reads disabled when no limit is enforced, or — when no budget is set. A coloured chip beneath the numbers names the action taken when the budget is exceeded: allow, throttle, or shadow.

Edit a budget

  1. Select the cell for the group and category you want to change. An editor opens, titled with the group and category (for example, general · api.read).
  2. Set Requests per window — the number of requests allowed in each window.
  3. Set Window seconds — the length of the window, in seconds.
  4. Set Burst — the number of requests allowed to exceed the steady rate for a short spike.
  5. Choose an Action:
    • allow (metered, never blocked) — count the requests but never block them.
    • throttle (429 + Retry-After) — block requests over the budget and ask the caller to retry later.
    • shadow (log-only) — record what would have been blocked without actually blocking it.
  6. Select or clear Enabled to turn enforcement of this cell on or off.
  7. Select Save. A confirmation message reports the group and category you updated, and the cell refreshes with its new values. To close without saving, select Cancel.