Closed vitalytarasov closed 2 years ago
You can set a higher harvest time with nrSetHarvestTime
to reduce the number of requests (default harvest time is 10 seconds).
Closing due to inactivity.
Closing the issue does not resolve the core problem - why is NR service rejecting requests from its own clients?
Hello @vitalytarasov I gave you a tip and I didn't get any feedback, that's why I closed the issue. Without further information, there is not much we can do. Have you tried doing it? If so, please give us more information about it, did it work or at least improved it? Also, what is the agent version you are using?
The Event API has a rate limit of 100,000 HTTP requests (POSTs) per minute, per account (https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/introduction-event-api/#post-limit). Are you using the same account for other apps? As I said, increasing the harvest time will reduce the number of requests, you could try 60 seconds and see if it improves the situation.
Thank you. I will raise the issue of rate limiting with our account manager.
Client makes POST requests excessively, NR services rate-limiti events with 429. Almost 80% of POST requests are rejected and retried which is a wasteful use of limited Roku device resources. See Charles session example at https://www.ridgepost.com/session.chls with lots of 429 errors.