topic Re: Response time degradation problem did not occur as we expected in Dashboarding

Response time degradation problem did not occur as we expected

ntanaka — Mon, 10 May 2021 12:58:12 GMT

Hi!

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.

I referred this document and found the description "Applications and services have to run for at least 20% of a week before slowdown and error rate alerts are raised"

https://www.dynatrace.com/support/help/monitor/pro...

However, I calculated the run ration and the result is over 20 %.
I referred Settings > Anomaly detection > Services and found an option "To avoid over-alerting do not alert for low load services with less than 10 requests/min."
However, I calculate the average value of requests to this service during 7 days before Feb 8th, then the result is over 10 requests/min.

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?

Best Regards,

Natsumi Tanaka

Re: Response time degradation problem did not occur as we expected

franz_soengen — Fri, 15 Feb 2019 12:42:23 GMT

Hi Natsumi,

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?

best regards
Franz

Re: Response time degradation problem did not occur as we expected

ntanaka — Fri, 15 Feb 2019 12:51:08 GMT

Hi Franz,

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%.

Re: Response time degradation problem did not occur as we expected

wolfgang_beer — Fri, 15 Feb 2019 14:00:00 GMT

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:

https://www.dynatrace.com/support/help/monitor/problems/problem-detection/how-are-new-problems-evaluated-and-raised/

Re: Response time degradation problem did not occur as we expected

ntanaka — Tue, 19 Feb 2019 13:53:15 GMT

Hi Wolfgang,

Thank you for your comment,

I will read the document you mentioned.