Dear Peter,

   Thanks for reaching out to us in the community. As I understand, our support folk have increased the threshold to 45 seconds. However, I understand the need for this setting to be configurable. There are some technicalities we need to iron out and hence are evaluating this and before giving to everyone. 

I'm just curious to know the nature of the REST API you are monitoring here. Is it a stream that the api gives or a micro service that you provide? 

Secondly, Is 30-45 sec a normal behavior for an API response in your case ? Any details you would like to share would be fascinating to understand. 

-Jasper 

PM, Site24x7

Hi Peter and Jasper, 

We are looking for this too. 

Did you get any resolution anywhere?

To answer Jasper's question (Secondly, Is 30-45 sec a normal behavior for an API response in your case ?), the answer is "yes". 

Our use-case:

We have a backend that depends on synchronous third-party systems.

1. From Site 24x7 we make a request to our backend,
2. The backend does a few things, and then sends a request to a third-party system. 
3. The third-party system responds to the backend
4. The back end processes the data received
5. The back end responds to Site 24x7

The time between #2 and #3 is highly unpredictable, as the third party, sometimes, takes 3 seconds, and some other times takes 45-90 seconds. Therefore, we would like to raise the Read Timeout to 110 seconds to avoid getting non-actionable alerts all around the place. 

I hope this answers the question. Please feel free to reach out via my email below if we need to discuss anything regarding this. 

Thank you, 

Abhishek Madhu

(abhishek.madhu@stratavar.com)