You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 :
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.
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 :Is there a way to setup an effective "per second" quota on Api Key ?
Should we consider another configuration for OTOROSHI_THROTTLING_WINDOW ?
The text was updated successfully, but these errors were encountered: