Stuck on Messaging WebSocket 429 errors during JMeter spike

General Discussion
1

Stuck on 429 Too Many Requests errors when pushing 200 concurrent WebSocket connections to /api/v2/analytics/metrics/conversations. The rate limit header resets too slowly for our load test ramp-up.

  • Tried increasing JMeter thread group ramp-up time from 10s to 60s.
  • Verified API key permissions include full analytics scope.
2

The documentation actually says WebSocket rate limits are enforced per tenant, not per API key, so spreading load across keys won’t help.

Switch to batch analytics queries or increase the JMeter ramp-up significantly to stay under the 100 req/s threshold.

3

The documentation actually says WebSocket streaming is not intended for high-throughput load testing; use the batch metrics API instead. Switching to POST /api/v2/analytics/query allows you to aggregate data in chunks, bypassing the per-tenant WebSocket throttle entirely.

4

If I remember correctly… the batch endpoint is the only reliable path here, as detailed in Support Article 9942-B.