[Bug]: Advanced Rate Limit not applying globally even when defined globally
Open
@renuka-fernando is already working on this.
Since Jul 7, 2026.
Area/Management
Aspect/API
Severity/Major
Type/Bug
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Management (Management API or Management Portal UI)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
When advanced-ratelimit policy is configured at an API-level, without specifying the keyExtraction as apiname, it is default to resource level leading it to act as though a resource-level ratelimit policy.
Steps to Reproduce
- Create LLM Proxy
- Attach global rate-limit policy via the rate-limit configuring tab in the AI Workspace/ advanced-rate-limit policy via the Guardrails & Policies tab.
- Deploy and invoke to verify the ratelimiting
Severity Level of the Issue
Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.