Set quota policy on edge microgateway for each consumer app/developer

[pallavjoshi]

We’ve been trying to implement Quota Policy in Apigee Microgateway. So far, we have been able to successfully implement Quota (approximate as guide says) on Product level. But we were unable to implement the same on a consumer to consumer basis for a product (quota for each app/developer).

On further research, we found that Apigee Edge uses an element called Identifier to configure the policy (https://docs.apigee.com/api-platform/reference/policies/quota-policy#identifierelement) but we couldn’t find any similar element or built-in configuration on Microgateway level.
Is there any built-in configuration to implement the same on Microgateway level? If not, how can we implement quota policy per consumer on Microgateway?

[Former Community Member]

The quota policy in Microgateway is at the app level. The quota configuration is set at the product, however the quota identifier is the apikey (aka developer app).

An excellent explanation of the quota plugin can be found here.

[pallavjoshi]

Hello @srinandans We're still unclear on this issue, shared blog post talk more about calculation of quota based on no. of child processes. It would be helpful if you could explain further with respect to the issue we are facing. Just to demonstrate the issue we will try to put up a relative example. We have two consumer apps of the same API product, App1 and App2. Now we are trying to limit the number of requests using Quota Policy for both of them 'separately'. By separately, we mean x number of permissible requests for App1 and y requests for App2. Is this kind of configuration possible for two or more than two Apps of a Product on a Microgateway?

[Former Community Member]

The quota identifier is the consumer key/api key. When the API is called using App1's apikey the counter is incremented against App1, same for App2. I have tried this 2.5.19 and works exactly as you have described it.