Hi,
My organization recently bought the enterprise version of Apigee and since then I have observed inconsistencies while implementing Quota Policy.
I followed the 4-minute Apigee Playlist and yet it fails. The Distributed flag is also set to true to ensure the issue is not because of 2 message processors.
I have gone through the following posts on the same subject
1. https://community.apigee.com/questions/60903/quota-policy-is-working-inconsistently.html
2. https://community.apigee.com/questions/45796/quota-usedavailable-count-inconsistent.html
Quota Policy
Trace Request Transaction Log
If anyone has come across such issue on the enterprise version and was able to fix it, appreciate the help.
Thanks
You said "inconsistencies" and "it fails" but you did not describe in detail what you are observing. I suppose that you mean that you are expecting the Quota policy to limit the call, but it does not.
It looks like the configuration is set for 5 requests per month, but you're able to send 10 or more requests into the system.
Can you set the Identifier element in the quota policy, like this:
<Identifier ref="apiproxy.name" />
adding the Identifier element didn't help.
Found a workaround(not the right approach).
If we set variables Distributed & Synchronous to false and set twice the quota than expected(based on the number of message processors).
The quota policy works fine, but don't want to use this approach.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |