NeophyteNeophyteHello everyone
I have now received feedback from LM that on March 26, 2024 auto throttling for external API calls was activated and therefore the 503 HTTP errors are coming (nowhere mentioned in the releases note, etc.).
The feedback from LM on my question how we can handle such errors in the future was simply "script a catch and try again after a certain time".
What do you think about this? Is this our problem now if the API has resource bottlenecks? Is LM leaving us to our fate here? Should LM increase the resources of the API?
In my opinion, a 429 HTTP error would be the right "procedure".
1. for 429 errors, the person who makes a request can do something about it AND also do something against it.
2. in the case of 503 errors, the person making the request can usually do nothing about it if there is a high load on the API AND also do nothing against it.
Have a nice weekend soon
Dorian
Auto throttling?
"script a catch and try again after a certain time"
What Joe_Williams posted earlier is what they mean by this.
A 429 would be the right thing to do as it explicitly means you've hit the rate limit. Sending back a 503 indicates that the server is having issues, not that there's anything wrong with our request.
ProfessorLM has always had rate limiting and it's documented at https://www.logicmonitor.com/support/rest-api-developers-guide/overview/rest-api-rate-limit. Is this something different or is it no longer doing 429 anymore?
