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.
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?
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.
@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.
