# Netdata alarm notifications not stopping even after updating "to: " field from sysadmin to silent

**URL:** <https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811>\
**Category:** Help\
**Tags:** agent\
**Created:** [January 21, 2021, 12:06pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811 "2021-01-21T12:06:28Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahul.sinha](https://avatars.discourse-cdn.com/v4/letter/r/dc4da7/32.png) [@rahul.sinha](https://community.netdata.cloud/u/rahul.sinha)\
**Post date:** [January 21, 2021, 12:06pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/1 "2021-01-21T12:06:29Z")

</div>

## Environment

Netdata docker container v1.28.0

## Problem

I am trying to disable some alarm notifications which I am getting because the behaviour is somewhat expected. E.g.  
10min\_cpu\_usage.  
I have updated the file using the edit-config and made “to: silent” for the 10min\_cpu\_usage alarm.

Contents of the /etc/netdata/health.d/cpu.conf

# you can disable an alarm notification by setting the ‘to’ line to: silent

template: 10min\_cpu\_usage  
on: system.cpu  
os: linux  
hosts: \*  
lookup: average -10m unaligned of user,system,softirq,irq,guest  
units: %  
every: 1m  
warn: $this \> (($status \>= $WARNING) ? (75) : (85))  
crit: $this \> (($status == $CRITICAL) ? (85) : (95))  
delay: down 15m multiplier 1.5 max 1h  
info: average cpu utilization for the last 10 minutes (excluding iowait, nice and steal)  
to: silent

template: 10min\_cpu\_iowait  
on: system.cpu  
os: linux  
hosts: \*  
lookup: average -10m unaligned of iowait  
units: %  
every: 1m  
warn: $this \> (($status \>= $WARNING) ? (20) : (40))  
crit: $this \> (($status == $CRITICAL) ? (40) : (50))  
delay: down 15m multiplier 1.5 max 1h  
info: average CPU wait I/O for the last 10 minutes  
to: sysadmin

template: 20min\_steal\_cpu  
on: system.cpu  
os: linux  
hosts: \*  
lookup: average -20m unaligned of steal  
units: %  
every: 5m  
warn: $this \> (($status \>= $WARNING) ? (5) : (10))  
crit: $this \> (($status == $CRITICAL) ? (20) : (30))  
delay: down 1h multiplier 1.5 max 2h  
info: average CPU steal time for the last 20 minutes  
to: sysadmin

## FreeBSD

template: 10min\_cpu\_usage  
on: system.cpu  
os: freebsd  
hosts: \*  
lookup: average -10m unaligned of user,system,interrupt  
units: %  
every: 1m  
warn: $this \> (($status \>= $WARNING) ? (75) : (85))  
crit: $this \> (($status == $CRITICAL) ? (85) : (95))  
delay: down 15m multiplier 1.5 max 1h  
info: average cpu utilization for the last 10 minutes (excluding nice)  
to: sysadmin

## What I expected to happen

I expected the alarm notification mails for cpu to be stopped.

## What is happening

I am still getting mails for this alarm.

 ![image](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/1X/a7df0fe8a384aff82050c9e692452d896ee676ae.png) **strong text**

---

<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:** [January 21, 2021, 3:49pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/2 "2021-01-21T15:49:53Z")

</div>

Hi @rahul.sinha

You didn’t mention in the OP - have you restarted the container after the changes?

---

<div class="post-metadata">

**Author:** ![rahul.sinha](https://avatars.discourse-cdn.com/v4/letter/r/dc4da7/32.png) [@rahul.sinha](https://community.netdata.cloud/u/rahul.sinha)\
**Post date:** [January 21, 2021, 6:38pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/3 "2021-01-21T18:38:23Z")

</div>

Hi @ilyam8 …sorry missed to mention… yes… after I did the changes, I did a netdatacli reload-health followed by a docker restart netdata\_container.

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.netdata.cloud/u/Daniel)\
**Post date:** [January 25, 2021, 6:06am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/4 "2021-01-25T06:06:43Z")

</div>

I’m seeing exactly the same thing. I’m not using a Docker container though, just running Netdata on vanilla Debian. I definitely restarted Netdata after editing the config.

What appears to be common between @rahul.sinha and me is that we’re both using Netdata Cloud - The screenshot looks like the Netdata Cloud email template rather than the standard Netdata one. Is it possible that cloud is not handling this `to` field in the config properly?

---

<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:** [January 25, 2021, 9:14am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/5 "2021-01-25T09:14:08Z")

</div>

@Daniel indeed!

@Leonidas_Vrachnis could you help?

`to: silent` is [the way to silence individual alarms](https://learn.netdata.cloud/docs/monitor/configure-alarms#silence-an-individual-alarm), seems like Netdata Cloud doesnt respect it.

---

<div class="post-metadata">

**Author:** ![rahul.sinha](https://avatars.discourse-cdn.com/v4/letter/r/dc4da7/32.png) [@rahul.sinha](https://community.netdata.cloud/u/rahul.sinha)\
**Post date:** [January 29, 2021, 5:30am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/6 "2021-01-29T05:30:30Z")

</div>

Hi guys, any help here please… got really stuck in this. Appreciate.

---

<div class="post-metadata">

**Author:** ![lordpengwin](https://avatars.discourse-cdn.com/v4/letter/l/48db29/32.png) [@lordpengwin](https://community.netdata.cloud/u/lordpengwin)\
**Post date:** [February 21, 2021, 3:46pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/7 "2021-02-21T15:46:41Z")

</div>

I’m seeing the same thing and am resorting to setting the thresholds to unrealistically high values.

---

<div class="post-metadata">

**Author:** ![Leonidas\_Vrachnis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/leonidas_vrachnis/32/156_2.png) [@Leonidas\_Vrachnis](https://community.netdata.cloud/u/Leonidas_Vrachnis)\
**Post date:** [February 22, 2021, 9:54am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/8 "2021-02-22T09:54:52Z")

</div>

> [@ilyam8](#):
>
> `to: silent` is [the way to silence individual alarms](https://learn.netdata.cloud/docs/monitor/configure-alarms#silence-an-individual-alarm), seems like Netdata Cloud doesnt respect it.

Indeed, the cloud doesn’t respect this config (actually is not even aware of this). Seems like an important feature that we are missing here, I will make sure product is aware.

---

<div class="post-metadata">

**Author:** ![Manos\_Saratsis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/manos_saratsis/32/158_2.png) [@Manos\_Saratsis](https://community.netdata.cloud/u/Manos_Saratsis)\
**Post date:** [February 23, 2021, 6:32pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/9 "2021-02-23T18:32:52Z")

</div>

@rahul.sinha @Daniel Currently the Cloud does not respect the “to: silent” configuration, we will improve this the upcoming weeks

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.netdata.cloud/u/Daniel)\
**Post date:** [March 5, 2021, 4:26am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/10 "2021-03-05T04:26:59Z")

</div>

Is there any ETA for this to be fixed in Netdata Cloud?

> [@lordpengwin](#):
>
> am resorting to setting the thresholds to unrealistically high values.

That’s a good idea as a temporary workaround. My workaround was adding an email filter that drops the emails.

---

<div class="post-metadata">

**Author:** ![Ryan\_S\_Di\_Francesco](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ryan_s_di_francesco/32/655_2.png) [@Ryan\_S\_Di\_Francesco](https://community.netdata.cloud/u/Ryan_S_Di_Francesco)\
**Post date:** [April 6, 2021, 12:57am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/11 "2021-04-06T00:57:26Z")

</div>

@Manos_Saratsis is there any ETA for this improvement? Anxious to roll Netdata out across our fleet, but can’t as we’re currently getting flooded with alerts in our testing.

---

<div class="post-metadata">

**Author:** ![OdysLam](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/odyslam/32/98_2.png) [@OdysLam](https://community.netdata.cloud/u/OdysLam)\
**Post date:** [April 6, 2021, 10:40am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/12 "2021-04-06T10:40:42Z")

</div>

Hey @Ryan_S_Di_Francesco,

Thanks for circling back to this. Manos is currently OOF, but let me check with the product team and we will get back to you!

---

<div class="post-metadata">

**Author:** ![harris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/harris/32/595_2.png) [@harris](https://community.netdata.cloud/u/harris)\
**Post date:** [April 6, 2021, 4:02pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/13 "2021-04-06T16:02:27Z")

</div>

Hopefully, we will have it fixed by the end of the next week 🤞

---

<div class="post-metadata">

**Author:** ![harris](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/harris/32/595_2.png) [@harris](https://community.netdata.cloud/u/harris)\
**Post date:** [April 9, 2021, 7:02am UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/14 "2021-04-09T07:02:07Z")

</div>

We have deployed the aforementioned enhancement.

Feel free to restart your agents and let us know if you have stopped receiving emails when the alert is configured with `to: silent`.

---

<div class="post-metadata">

**Author:** ![OdysLam](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/odyslam/32/98_2.png) [@OdysLam](https://community.netdata.cloud/u/OdysLam)\
**Post date:** [April 9, 2021, 2:39pm UTC](https://community.netdata.cloud/t/netdata-alarm-notifications-not-stopping-even-after-updating-to-field-from-sysadmin-to-silent/811/15 "2021-04-09T14:39:42Z")

</div>

Thanks @harris for circling back so rapidly. Awesome!
