15 Feb 2019 04:34 AM - last edited on 10 May 2021 05:58 AM by MaciejNeumann
We experienced over 10 seconds response time of a certain service on Feb 8th but Dynatrace did not detect it.
We could not find red zone on this graph.
There is no problem on this service detail page.
I confirmed the following 2 points but I am not sure why Response time degradation problem did not occur as we expected.
Please see the result of calculation theresultofcalculation.xlsx
Do you think what I confirmed is beside the point?
Could you please let me know the other point I should confirm in order to enable Dynatrace to detect response degradation of this service?
Solved! Go to Solution.
you mentioned the point of "Applications and services have to run for at least 20% of a week before slowdown and error rate alerts are raised" and said that you calculated the runtime to be higher than that.
This service seems to have had it's first request at 9am though and the increase in response time started at 11am. That's only 2 hours and therefore less than 20% of a week. Am I missing something here?
Thank you for your reply!
The document says 20% of a week, so I calculated the requests from Feb 1 to Feb 7.
Please see this graph.
This graph also shows the run time is higher than 20%.
The running time has to be more than 20% of 7 days and you need at least around 10 requests per minute load. If you would like to have a strict alert for low load infrequent running services you can set a static threshold. See help topic here:
Thank you for your comment,
I will read the document you mentioned.