You need a working
sendmail command for email alerts to work. Almost all MTAs provide a
Netdata sends all emails as user
netdata, so make sure your
sendmail works for local users.
email notifications look like this:
health_alarm_notify.conf on your system run
You can configure recipients in
You can also configure per role recipients in the same file, a few lines below.
Changes to this file do not require a Netdata restart.
You can test your configuration by issuing the commands:
# become user netdata
sudo su -s /bin/bash netdata
# send a test alarm
/usr/libexec/netdata/plugins.d/alarm-notify.sh test [ROLE]
[ROLE] is the role you want to test. The default (if you don't give a
Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under
You can always find the location of the alarm-notify.sh script in
Every notification email (both the plain text and the rich html versions) from the Netdata agent, contain a set of custom email headers that can be used for filtering using an email client. Example:
Simple SMTP transport configuration
If you want an alternative to
sendmail in order to have a simple MTA configuration for sending emails and auth to an existing SMTP server, you can do the following:
- Modify the
health_alarm_notify.confto point to the location of
# The full path to the sendmail command.
# If empty, the system $PATH will be searched for it.
# If not found, email notifications will be disabled (silently).
- Login as netdata :
(sudo) su -s /bin/bash netdata
~/.msmtprcas shown in the documentation.
- Finally set the appropriate permissions on the
chmod 600 ~/.msmtprc