Add 4 sec / 8 sec to the Apdex threshold dropdown
Some APIs are slower than others but it doesn't mean that they give a bad experience to the client.
An API which has a response time of 5sec by design, currently shows up with red bars on the monitors page which is bad to show on a customer facing monitor page.
The 4s and 8s Apdex T have just been added: https://headwayapp.co/updown-release-notes/slower-4s-and-8s-apdex-thresold-260571
Please use them wisely :)
-
Gautier MICHELIN commented
Hi @Adrien,
Ok, in fact I'm using my own metrics for some servers, as I have with most of my end customers (I'm working with museums) only a need for a metric during business hours, and only to check if server is up or down without response time.
I've build it lately now through the API. Seeing this request, a metric of 4s would have been enough (as we don't monitor pro servers at night) to have an average, displaying it through your public interface (quite nice and very efficient btw).So, for me, no real need immediately.
-
Hi @Gautier, this request stays open to measure interest. I haven't planned to add any slower Apdex threshold value for the moment, as this additional values would increase storage for all checks. Which use-case do you have were a 2s+ response time should be considered satisfactory?
-
Gautier MICHELIN commented
Hi @Adrien, please update us with the status of this request.
-
TestingSmartIP commented
Sounds good. I proposed 5sec just as an example, but 4 and 8 sec selections would be great.
-
Numbers like 5 sec will never be added because it needs to be a power of two (this is because we need to store the number of requests under ApdexT and ApdexT*4, so using power of 2 allows to reuse more numbers). So the next values that could be added without causing too much overhead are 4s and 8s. I'll update this suggestion to reflect this and leave it open to measure the interest.