What’s the best way to handle rate limits on the analytics api during load testing?
we are running jmeter 5.6.2 to simulate high concurrency. specifically we are hitting the /api/v2/analytics/interactions/realtime endpoint. the goal is to check how the dashboard handles sudden spikes in call volume. we have a script that sends 50 requests per second from 10 virtual users.
after about 30 seconds we start getting 429 too many requests errors. the response header says retry-after: 1. we tried adding a random delay between 500ms and 2s but it still fails under heavy load. the documentation mentions a limit of 10 requests per second per tenant but i am not sure if that applies to this specific endpoint or if it is per api key.
is there a way to increase the limit for testing purposes? or should we be using a different endpoint for bulk data retrieval? we are using the default auth flow with client credentials. any help would be appreciated. the error logs are attached below.
status_code: 429
error: rate_limit_exceeded