cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue with incident rule when URL monitor and DB monitor are combined

s_nolfi
Participant

Hello,

we are having some problem with an incident that is not working well, our incident is composed by measures from URL monitors and DB monitor in logic and/or, follows a screenshot:

Except for DB connection all measures come from URL monitors.

We have another incident that monitors just DB

Now, we have saw that when DB connection is violated, "Rete Applicativa -Database" does not trigger:

The strange thing is that if we remove the measure "DB Connection" from conditions of "Rete Applicativa -Database" the incident works good. Does somebody have any idea about this behavior and how to fix it?

Thanks in advance

Simone


2 REPLIES 2

joao_vilacia2
Inactive

Hi, @Simone N.

It would be interesting to check the thresholds set for the two metrics to identify why the incident is not being triggered.

In other words, check the conditions that are being used because one of the conditions is not being evaluated correctly.


s_nolfi
Participant

Hi @João Luiz Vilacia B.

these are the thresholds (equals for all the incidents):

- SocketTimedOut: Lower Severe 0.01 (in order to filter SocketException)

- HostReachable: Lower Severe 0.99

- HttpStatusCode: Upper Severe 302

- DB Connection: Lower Severe 0.99

Timeframe: 5 minutes

Because "Database" triggered threshold was violated but i don't understand why "Rete Interna - Database" did not. Continuing with the analysis, without modifying anything, we have saw that when measures related to URL monitors were violated, in some cases incidents triggered, in other cases no without an apparent reasons for these different behaviors.

Suggestions?

Thanks in advance

Simone