APMIA APIJEE monitoring ERROR: HTTP 429 (Too Many Requests) error

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Depending on the number of Apigee X API Proxies being monitored, APMIA users as well might encounter this error in APMIS run logs, below is a sample error message:

error: code: 429,
    "message": "Quota exceeded for quota metric 'Metrics requests' and limit 'Metrics requests per minute' of service 'xxx.com' for consumer 'project_number:<>'.",
    "status": "RESOURCE_EXHAUSTED",

 

Environment

APMIA 2x version

Cause

The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time ("rate limiting").

GCP Apigee X has a default quota of a max of 100 metric requests per minute, if the number of metric requests exceeds the max limit of 100, a 429 (Too Many Requests) error is returned.

 

Resolution

Ways to handle the error:

• Increase the Apigee X API's 'Metrics requests per minute' quota:

Steps to increase the quota:

1. 1. Go to the link https://console.cloud.google.com/apis/api/apigee.googleapis.com/quotas?project=<gcp-project-id>.
   2. From the list of quotas listed on the page, update the limit of the 'Metrics requests per minute' quota for 'Apigee API' service.

• If you still encounter 429 error in the APMIA logs, calibrate the values of the below given request retry properties in the 'bundle.properties' file of the GCP Monitoring Extension
  1. introscope.agent.gcp.profiles.gcp.1.httpreq.retryInterval
  2. introscope.agent.gcp.profiles.gcp.1.httpreq.retryCount
  3. introscope.agent.gcp.profiles.gcp.1.httpreq.retryBatchSize