Browser clickpath outage handling

[SureshThakur]

Hi Team, 

Although, it is very clear from the description, but I still want to understand how this setting creates a problem.  Below is the outage alert config and same if found in attached image. 

Generate a problem and send an alert when this monitor is unavailable for one or more consecutive runs at any location
Alter if at least 1 location is unable to access my web application 3 times consecutively. 
Automatic retry on error -- Toggle is on 

I am expecting that alert should be raised once there are 3 continues failed execution. However, what I have observed is that even I get problem on 1 failed execution. 

Problem raised on first failed event



Can someone advice how does this setting work? 

Regards

Suresh 

[Akhil-Jayendran · Accepted solution]

Hi @SureshThakur ,

If you select the option “Alert if at least 1 location is unable to access my web application 3 times consecutively”, then a problem will be generated only if the synthetic monitor fails three times in a row in a location.

If you received a problem after just one failed execution, that’s unusual and should be investigated further.

in  the synthetic page there is a  tab for execution details similar like below have you checked there ? , As far as I know if you enabled the retry on error this will also count for execution.

[SureshThakur]

Hi Akhil, 
Thanks for your response. I am also bit confused on this retry functionality if every failed re-try counts to this threshold.  I will raise a ticket with Dynatrace to check how it works. Still, it is not making sense to get problem trigger on first failed event. No, idea if Dynatrace reports the re-try failed event to UI. 

[HannahM]

The event seen in your screenshot is the one triggered after the threshold for consecutive failures of your monitor is breached. If you check the executions, you'll see that there were three consecutive failures before the 'event' was triggered.

[SureshThakur]

Thank you, Hannah.

Sorry for delay, I did check this, and the problem did fire on second failed execution. However, I validated some other monitors and for them it is getting triggered after 3 failed executions. It may be a one isolated case.