Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Throttling quota doesn't block request ? #2067

Open
cbois opened this issue Jan 7, 2025 · 1 comment
Open

Throttling quota doesn't block request ? #2067

cbois opened this issue Jan 7, 2025 · 1 comment

Comments

@cbois
Copy link

cbois commented Jan 7, 2025

Hi !

As reported on discord channel, I'm performing some tests around Otoroshi GatewayEvents (for dashboarding and alerting purposes), mainly on Otoroshi Events fired when a client exceeds his apikey's quotas.
I'm facing an issue with "Throttling quota" on my Api Key.
image

  • Otoroshi version: 16.22.0
  • Datastore: PostGreSQL
  • Cluster mode

Our configuration of throttling windows is the default one : OTOROSHI_THROTTLING_WINDOW=10

When I spam my route with "parallel curls", exceeding throttling quota, Otoroshi doesn't block my calls (429?) nor throws any event with an explicit gwError.

You can see remainingQuotas from corresponding calls :

    "remainingQuotas": {
        "authorizedCallsPerSec": 1,
        "currentCallsPerSec": 9,
        "remainingCallsPerSec": -8,
        "authorizedCallsPerDay": 200000,
        "currentCallsPerDay": 212,
        "remainingCallsPerDay": 199788,
        "authorizedCallsPerMonth": 500000,
        "currentCallsPerMonth": 556,
        "remainingCallsPerMonth": 499444
    },

Is there a way to setup an effective "per second" quota on Api Key ?
Should we consider another configuration for OTOROSHI_THROTTLING_WINDOW ?

@Zwiterrion
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants