Before ResetQuota policy, the count for the id=“smg” was 96. After the ResetQuota it was 196, meaning the value in ResetQuota was added to current count - it was not reset to 100.
@sgilson , I can able to reproduce same, Policy name is misleading in this case. Ideally it should reset to original counter value instead of adding the count to existing available count. Yes, It doesn’t work on global identifier.
Thanks @Anil Sagar, based on how it seems to work, the ResetQuota policy should really be called “IncreaseQuota” or “TempIncreaseQuota” because the way it works is:
Add a value to available.count
Subtract that same value from used.count
Discard the changes when the Quota policy next resets
I am not able to post a question because the form keeps telling me that the description needs to be a minimum of 60 or something
Sorry if I hijacked this post with my question
I noticed that after I deploy my proxy for a long time, accepting numbers of traffic, the quota counter seems to be stuck at some point
My intention was to limit 60 active request simultaneously, and thus any request over that will hit the quota limit and receive a 429 message. I added a ResetQuota on the way out decrementing by the counter by one. However, I noticed that even though there are no active traffic going on, my quota counter shows usedCount at 6, availableCount at 54. I expected the availableCount to be back to 0 since I am decrementing one on every exit (both success and error)