| 1 | <!--startmeta |
| 2 | custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/health/notifications/signl4/README.md" |
| 3 | meta_yaml: "https://github.com/netdata/netdata/edit/master/src/health/notifications/signl4/metadata.yaml" |
| 4 | sidebar_label: "SIGNL4" |
| 5 | learn_status: "Published" |
| 6 | learn_rel_path: "Alerts & Notifications/Notifications/Agent Dispatched Notifications" |
| 7 | keywords: ['signl4'] |
| 8 | message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NOTIFICATION'S metadata.yaml FILE" |
| 9 | endmeta--> |
| 10 | |
| 11 | # SIGNL4 |
| 12 | |
| 13 | |
| 14 | <img src="https://netdata.cloud/img/signl4.svg" width="150"/> |
| 15 | |
| 16 | |
| 17 | SIGNL4 offers critical alerting, incident response and service dispatching for operating critical infrastructure. It alerts you persistently via app push, SMS text, voice calls, and email including tracking, escalation, on-call duty scheduling and collaboration. |
| 18 | You can send notifications to SIGNL4 using Netdata's Agent alert notification feature, which supports dozens of endpoints, user roles, and more. |
| 19 | |
| 20 | |
| 21 | <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> |
| 22 | |
| 23 | ## Setup |
| 24 | |
| 25 | |
| 26 | ### Prerequisites |
| 27 | |
| 28 | #### |
| 29 | |
| 30 | - An inbound webhook in SIGNL4 |
| 31 | - Access to the terminal where Netdata Agent is running |
| 32 | |
| 33 | |
| 34 | |
| 35 | ### Configuration |
| 36 | |
| 37 | #### Options |
| 38 | |
| 39 | The following options can be defined for this notification |
| 40 | |
| 41 | <details open><summary>Config Options</summary> |
| 42 | |
| 43 | |
| 44 | |
| 45 | | Option | Description | Default | Required | |
| 46 | |:-----|:------------|:--------|:---------:| |
| 47 | | SEND_SIGNL4 | Set `SEND_SIGNL4` to YES | YES | yes | |
| 48 | | SIGNL4_WEBHOOK_URL | set `SIGNL4_WEBHOOK_URL` to your SIGNL4 webhook URL. | | yes | |
| 49 | |
| 50 | |
| 51 | </details> |
| 52 | |
| 53 | |
| 54 | |
| 55 | #### via File |
| 56 | |
| 57 | The configuration file name for this integration is `health_alarm_notify.conf`. |
| 58 | |
| 59 | |
| 60 | You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the |
| 61 | Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory). |
| 62 | |
| 63 | ```bash |
| 64 | cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata |
| 65 | sudo ./edit-config health_alarm_notify.conf |
| 66 | ``` |
| 67 | |
| 68 | ##### Examples |
| 69 | |
| 70 | ###### Basic Configuration |
| 71 | |
| 72 | |
| 73 | |
| 74 | ```yaml |
| 75 | SEND_SIGNL4="YES" |
| 76 | SIGNL4_WEBHOOK_URL="https://connect.signl4.com/webhook/xxxxxxxx" |
| 77 | |
| 78 | ``` |
| 79 | |
| 80 | |
| 81 | ## Troubleshooting |
| 82 | |
| 83 | ### Test Notification |
| 84 | |
| 85 | You can run the following command by hand, to test alerts configuration: |
| 86 | |
| 87 | ```bash |
| 88 | # become user netdata |
| 89 | sudo su -s /bin/bash netdata |
| 90 | |
| 91 | # enable debugging info on the console |
| 92 | export NETDATA_ALARM_NOTIFY_DEBUG=1 |
| 93 | |
| 94 | # send test alarms to sysadmin |
| 95 | /usr/libexec/netdata/plugins.d/alarm-notify.sh test |
| 96 | |
| 97 | # send test alarms to any role |
| 98 | /usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE" |
| 99 | ``` |
| 100 | |
| 101 | Note that this will test _all_ alert mechanisms for the selected role. |
| 102 | |
| 103 |