topic Re: How work mechanism of closing the problem for Synthetic test in Alerting

How work mechanism of closing the problem for Synthetic test

MAkimov — Mon, 15 Feb 2021 07:38:57 GMT

Please help with the answer to the question on the mechanisms and logic of closing the Problem for events related to unavailability of synthetic tests.

I looked at the documentation and didn't find a description of our question.https://www.dynatrace.com/support/help/shortlink/synthetic-alerting

There are a number of synthetic tests set up.

as parameter Outage handling - the following parameter is set

Next, we receive events about the test unavailability. And the problem opens

In the following figure, we see two test fail events

Between the tests, we see two successful tests. Time between unsuccessful tests 15 minutes

Dynatrace does not close the problem at 03:17 - after the first successful test, but for some reason closed it at 03:32

we do not understand the mechanism of closing the problem.

Plus we have a task to send an escalating notification if the problem has been open for a long time, but with such an incorrect lifetime of the problem, we will receive erroneous escalations

Re: How work mechanism of closing the problem for Synthetic test

ChadTurner — Mon, 15 Feb 2021 14:37:46 GMT

It might be that Dynatrace is hanging onto the problem to ensure the issue doesn't arise again, other wise you might get an alert for a failure, then closure, then failure, then closure. we see this with purepath failures as well, where Dynatrace AI will keep a problem open for 10-15mins after the last failure is detected.

Re: How work mechanism of closing the problem for Synthetic test

MAkimov — Tue, 16 Feb 2021 07:32:48 GMT

thanks for the response!

I also assume that the problem lives for a certain time and closes when the condition is met.

I would like to understand exactly how this happens, otherwise I cannot set up escalation alerts.

Re: How work mechanism of closing the problem for Synthetic test

ChadTurner — Thu, 16 Dec 2021 15:44:24 GMT

@MAkimov has this gotten any better with the latest cluster and synthetic AG updates or are you still seeing the delayed closure?