Not all alarms send to the Telegram

Help
,
4

Hi @itohin

That is likely because of delay option.

This is used to provide optional hysteresis settings for the notifications, to defend against notification floods. These settings do not affect the actual alarm - only the time the exec script is executed.

So it delays sending a notification (up: CLEAR → WARN/CRIT, down: WARN/CRIT → CLEAR).

The log reflects the actual state of the alarm. Netdata Cloud uses the actual state and doesn’t respect delay (WIP to implement it).

Do Netdata Cloud and Netdata Agent have separate alarm settings?

Two different notifications dispatching pipelines.

1 Like