1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
|
<!--
title: "Enable notifications"
description: "Send Netdata's alerts to platforms like email, Slack, PagerDuty, Twilio, and more to enable incident response and faster resolution."
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/monitor/enable-notifications.md
-->
# Enable notifications
Netdata comes with a [notification system](/health/notifications/README.md) that supports more than a dozen services,
such as email, Slack, PagerDuty, Twilio, Amazon SNS, Discord, and much more. You can enable as many platforms as you
want, and configure them to match your organization's needs with features like role-based notifications.
## Supported notification platforms
- [**alerta.io**](/health/notifications/alerta/README.md)
- [**Amazon SNS**](/health/notifications/awssns/README.md)
- [**Custom endpoint**](/health/notifications/custom/README.md)
- [**Discord**](/health/notifications/discord/README.md)
- [**Dynatrace**](/health/notifications/dynatrace/README.md)
- [**Email**](/health/notifications/email/README.md)
- [**Flock**](/health/notifications/flock/README.md)
- [**Google Hangouts**](/health/notifications/hangouts/README.md)
- [**IRC**](/health/notifications/irc/README.md)
- [**Kavenegar**](/health/notifications/kavenegar/README.md)
- [**Matrix**](/health/notifications/matrix/README.md)
- [**Messagebird**](/health/notifications/messagebird/README.md)
- [**Netdata Agent dashboard**](/health/notifications/web/README.md)
- [**Opsgenie**](/health/notifications/opsgenie/README.md)
- [**PagerDuty**](/health/notifications/pagerduty/README.md)
- [**Prowl**](/health/notifications/prowl/README.md)
- [**PushBullet**](/health/notifications/pushbullet/README.md)
- [**PushOver**](/health/notifications/pushover/README.md)
- [**Rocket.Chat**](/health/notifications/rocketchat/README.md)
- [**Slack**](/health/notifications/slack/README.md)
- [**SMS Server Tools 3**](/health/notifications/smstools3/README.md)
- [**StackPulse**](/health/notifications/stackpulse/README.md)
- [**Syslog**](/health/notifications/syslog/README.md)
- [**Telegram**](/health/notifications/telegram/README.md)
- [**Twilio**](/health/notifications/twilio/README.md)
This doc covers enabling email and Slack notifications, but the same process applies to enabling any other notification
platform.
## Enable email notifications
To use [email notifications](/health/notifications/email/README.md), you need
[`sendmail`](http://www.postfix.org/sendmail.1.html) or an equivalent installed on your system.
Edit the `health_alarm_notify.conf` file, which resides in your Netdata [config
directory](/docs/configure/nodes.md#netdata-config-directory).
```bash
sudo ./edit-config health_alarm_notify.conf
```
Look for the following lines:
```conf
# if a role recipient is not configured, an email will be sent to:
DEFAULT_RECIPIENT_EMAIL="root"
# to receive only critical alarms, set it to "root|critical"
```
Change the value of `DEFAULT_RECIPIENT_EMAIL` to the email address at which you'd like to receive notifications.
```conf
# if a role recipient is not configured, an email will be sent to:
DEFAULT_RECIPIENT_EMAIL="me@example.com"
# to receive only critical alarms, set it to "root|critical"
```
Test email notifications system by first becoming the Netdata user and then asking Netdata to send a test alarm:
```bash
sudo su -s /bin/bash netdata
/usr/libexec/netdata/plugins.d/alarm-notify.sh test
```
You should see output similar to this:
```bash
# SENDING TEST WARNING ALARM TO ROLE: sysadmin
2019-10-17 18:23:38: alarm-notify.sh: INFO: sent email notification for: hostname test.chart.test_alarm is WARNING to 'me@example.com'
# OK
# SENDING TEST CRITICAL ALARM TO ROLE: sysadmin
2019-10-17 18:23:38: alarm-notify.sh: INFO: sent email notification for: hostname test.chart.test_alarm is CRITICAL to 'me@example.com'
# OK
# SENDING TEST CLEAR ALARM TO ROLE: sysadmin
2019-10-17 18:23:39: alarm-notify.sh: INFO: sent email notification for: hostname test.chart.test_alarm is CLEAR to 'me@example.com'
# OK
```
Check your email. You should receive three separate emails for each health status change: `WARNING`, `CRITICAL`, and
`CLEAR`.
See the [email notifications](/health/notifications/email/README.md) doc for more options and information.
## Enable Slack notifications
If you're one of the many who spend their workday getting pinged with GIFs by your colleagues, why not add Netdata
notifications to the mix? It's a great way to immediately see, collaborate around, and respond to anomalies in your
infrastructure.
To get Slack notifications working, you first need to add an [incoming
webhook](https://slack.com/apps/A0F7XDUAZ-incoming-webhooks) to the channel of your choice. Click the green **Add to
Slack** button, choose the channel, and click the **Add Incoming WebHooks Integration** button.
On the following page, you'll receive a **Webhook URL**. That's what you'll need to configure Netdata, so keep it handy.
Time to dive back into your `health_alarm_notify.conf` file:
```bash
sudo ./edit-config health_alarm_notify.conf
```
Look for the `SLACK_WEBHOOK_URL=" "` line and add the incoming webhook URL you got from Slack:
```conf
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXX/XXXXXXXXXXXX"
```
A few lines down, edit the `DEFAULT_RECIPIENT_SLACK` line to contain a single hash `#` character. This instructs Netdata
to send a notification to the channel you configured with the incoming webhook.
```conf
DEFAULT_RECIPIENT_SLACK="#"
```
Time to test the notifications again:
```bash
sudo su -s /bin/bash netdata
/usr/libexec/netdata/plugins.d/alarm-notify.sh test
```
You should receive three notifications in your Slack channel for each health status change: `WARNING`, `CRITICAL`, and
`CLEAR`.
See the [Slack notifications](/health/notifications/slack/README.md) doc for more options and information.
## What's next?
Learn more about Netdata's notifications system in the [notifications](/health/notifications/README.md) docs.
Now that you have health entities configured to your infrastructure's needs, and notifications to inform you of
anomalies, you have everything you need to monitor the health of your infrastructure. To make your dashboards most
useful during root cause analysis, you can use Netdata's [distributed data
architecture](/docs/store/distributed-data-architecture.md) for the best-in-class performance and scalability.
[](<>)
|
