Analytics API 429 errors during high-volume load test

Looking for advice on handling rate limits when pulling queue metrics via /api/v2/analytics/queues/summary. Our JMeter script hits the endpoint every 5 seconds for 500 concurrent agents, and we start getting 429 Too Many Requests after about 10 minutes. This blocks our capacity planning validation.

Is there a specific backoff strategy recommended for this endpoint? The standard retry logic does not seem to help when the queue depth is high. We are on Genesys Cloud US1 with JMeter 5.6.2.

TL;DR: Switch to batch analytics.

The easiest way to fix this is to stop polling every 5 seconds and use the /api/v2/analytics/bulk endpoint instead. It handles higher throughput natively and prevents the 429s from killing your JMeter run.