# Not all alarms send to the Telegram

**URL:** <https://community.netdata.cloud/t/not-all-alarms-send-to-the-telegram/1263>\
**Category:** Help\
**Tags:** agent-alarms, agent\
**Created:** [May 7, 2021, 7:46am UTC](https://community.netdata.cloud/t/not-all-alarms-send-to-the-telegram/1263 "2021-05-07T07:46:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [May 7, 2021, 12:39pm UTC](https://community.netdata.cloud/t/not-all-alarms-send-to-the-telegram/1263/4 "2021-05-07T12:39:01Z")

</div>

Hi @itohin

That is likely because of [delay](https://learn.netdata.cloud/docs/agent/health/reference#alarm-line-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](https://github.com/netdata/netdata/issues/10896#issuecomment-812591403).

---

_[View the full topic](https://community.netdata.cloud/t/not-all-alarms-send-to-the-telegram/1263)._