The delay of my HTTP notification is about 3 Minutes from the failure until the notification is actually being sent. How can i make the webhook sending immediately (or after the defined time in the notification settings of the sensor) after the sensor changed it's state?

Article Comments

Hello,

If you set the timer in the trigger settings to 0, the trigger will execute the notification template immediately. What scanning intervals do you have on the sensor in question, and what timing do you have in the trigger itself?

Benjamin Day
[Paessler Support]


Sep, 2022 - Permalink

Hi, the scanning interval is 30 seconds. The trigger timer is set to 60 seconds. Email notifications are sent directly after this 60 seconds. Example from the protocol: 08.09.2022 01:12:53 HTTP Sensor: Socket error: connection timed out (now the 60 seconds should begin to run) 08.09.2022 01:17:22 HTTP-Notification triggered by this sensor id and sent according to protocol


Sep, 2022 - Permalink

Hello,

Yes, so the sensor is scanning twice before the trigger would kick off in your case. I would recommend you change the timing on the trigger to 30 seconds, or 0 seconds to get the alerting as quickly as possible.

Benjamin Day
[Paessler Support]


Sep, 2022 - Permalink

Hello, i tried to set the trigger timer to 0s. Here is a protocol snippet:

14.09.2022 18:57:27 Fehler 8.748 ms (Ladezeit) liegt über dem Fehlergrenzwert von 8.000 ms in Ladezeit
[...]
14.09.2022 18:57:49 OK 50ms
[...]
14.09.2022 19:00:49 Notification alert about the sensor error
14.09.2022 19:00:49 Notification alert about the sensor status back to normal

It seems that the notifications are sent bachwise all n minutes. I also need to set the trigger to at least 31 seconds because a short outage is allowed.

Here is a screenshot of the protocol: https://imgur.com/a/fUgKC0F


Sep, 2022 - Permalink

Hello,

Yes, you could switch it to 31 seconds to take into account the 30 second scanning interval.

Benjamin Day
[Paessler Support]


Sep, 2022 - Permalink