diff options
| author | Promise Akpan <akpanpromise@hotmail.com> | 2019-08-15 12:06:39 +0100 |
|---|---|---|
| committer | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2019-08-15 13:06:39 +0200 |
| commit | f5006d51e8caf9148d393eb68d53dc9fcd28b7b6 (patch) | |
| tree | 03b757236d6b45e46813a4a875c77dc775e5f896 /health/notifications | |
| parent | 69172fd57472df75d877f43de2dcc693c48ab5c0 (diff) | |
Fix Markdown Lint warnings (#6664)
* make remark access all directories
* detailed fix after autofix by remark lint
* cross check autofix for this set of files
* crosscheck more files
* crosschecking and small fixes
* crosscheck autofixed md files
Diffstat (limited to 'health/notifications')
20 files changed, 159 insertions, 151 deletions
diff --git a/health/notifications/README.md b/health/notifications/README.md index 8c7ab66f75..a0065729a3 100644 --- a/health/notifications/README.md +++ b/health/notifications/README.md @@ -7,9 +7,9 @@ You can change the default script globally by editing `/etc/netdata/netdata.conf `alarm-notify.sh` is capable of sending notifications: -- to multiple recipients -- using multiple notification methods -- filtering severity per recipient +- to multiple recipients +- using multiple notification methods +- filtering severity per recipient It uses **roles**. For example `sysadmin`, `webmaster`, `dba`, etc. @@ -23,23 +23,23 @@ Each role may have one or more destinations. So, for example the `sysadmin` role may send: -1. emails to admin1@example.com and admin2@example.com -2. pushover.net notifications to USERTOKENS `A`, `B` and `C`. -3. pushbullet.com push notifications to admin1@example.com and admin2@example.com -4. messages to slack.com channel `#alarms` and `#systems`. -5. messages to Discord channels `#alarms` and `#systems`. +1. emails to admin1@example.com and admin2@example.com +2. pushover.net notifications to USERTOKENS `A`, `B` and `C`. +3. pushbullet.com push notifications to admin1@example.com and admin2@example.com +4. messages to slack.com channel `#alarms` and `#systems`. +5. messages to Discord channels `#alarms` and `#systems`. ## Configuration Edit [`/etc/netdata/health_alarm_notify.conf`](health_alarm_notify.conf) by running `/etc/netdata/edit-config health_alarm_notify.conf`: -- settings per notification method: +- settings per notification method: - all notification methods except email, require some configuration - (i.e. API keys, tokens, destination rooms, channels, etc). + all notification methods except email, require some configuration + (i.e. API keys, tokens, destination rooms, channels, etc). -2. **recipients** per **role** per **notification method** +2. **recipients** per **role** per **notification method** ## Testing Notifications @@ -62,8 +62,10 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1 Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under `/usr/lib/netdata`). You can always find the location of the alarm-notify.sh script in `netdata.conf`. If you need to dig even deeper, you can trace the execution with `bash -x`. Note that in test mode, alarm-notify.sh calls itself with many more arguments. So first do - ```sh - bash -x /usr/libexec/netdata/plugins.d/alarm-notify.sh test - ``` + +```sh +bash -x /usr/libexec/netdata/plugins.d/alarm-notify.sh test +``` + Then look in the output for the alarm-notify.sh calls and run the one you want to trace with `bash -x`. -[]() +[](<>) diff --git a/health/notifications/alerta/README.md b/health/notifications/alerta/README.md index 2826fe7737..a34d2b796c 100644 --- a/health/notifications/alerta/README.md +++ b/health/notifications/alerta/README.md @@ -26,7 +26,9 @@ configurations are out os scope of this tutorial but information about different deployment scenaries can be found in the [docs][3]. [1]: https://hub.docker.com/r/alerta/alerta-web/ + [2]: http://alerta.readthedocs.io/en/latest/gettingstarted/tutorial-1-deploy-alerta.html + [3]: http://docs.alerta.io/en/latest/deployment.html ## Send alarms to Alerta @@ -42,7 +44,9 @@ Step 2. configure Netdata to send alarms to Alerta On your system run: - $ /etc/netdata/edit-config health_alarm_notify.conf +```sh +/etc/netdata/edit-config health_alarm_notify.conf +``` and modify the file as below: @@ -70,13 +74,15 @@ DEFAULT_RECIPIENT_ALERTA="Production" We can test alarms using the standard approach: - $ /opt/netdata/netdata-plugins/plugins.d/alarm-notify.sh test +```sh +/opt/netdata/netdata-plugins/plugins.d/alarm-notify.sh test +``` Note: Netdata will send 3 alarms, and because last alarm is "CLEAR" you will not see them in main Alerta page, you need to select to see "closed" alarma in top-right lookup. A little change in `alarm-notify.sh` that let us test each state one by one will be useful. -For more information see [https://docs.alerta.io](https://docs.alerta.io) +For more information see <https://docs.alerta.io> -[]() +[](<>) diff --git a/health/notifications/awssns/README.md b/health/notifications/awssns/README.md index 7bb3487143..ed838dacb9 100644 --- a/health/notifications/awssns/README.md +++ b/health/notifications/awssns/README.md @@ -2,23 +2,25 @@ As part of it's AWS suite, Amazon provides a notification broker service called 'Simple Notification Service' or SNS. Amazon SNS works kind of similarly to Netdata's own notification system, allowing dispatch of a single notification to multiple subscribers of different types. Among other things, SNS supports sending notifications to: -* Email addresses. -* Mobile Phones via SMS. -* HTTP or HTTPS web hooks. -* AWS Lambda functions. -* AWS SQS queues. -* Mobile applications via push notifications. +- Email addresses. +- Mobile Phones via SMS. +- HTTP or HTTPS web hooks. +- AWS Lambda functions. +- AWS SQS queues. +- Mobile applications via push notifications. To get this working, you will need: -* The Amazon Web Services CLI tools. Most distributions provide these with the package name `awscli`. -* An actual home directory for the user you run Netdata as, instead of just using `/` as a home directory. Setup of this is distribution specific. `/var/lib/netdata` is the recommended directory (because the permissions will already be correct) if you are using a dedicated user (which is how most distributions work). -* An Amazon SNS topic to send notifications to with one or more subscribers. The [Getting Started](https://docs.aws.amazon.com/sns/latest/dg/GettingStarted.html) section of the Amazon SNS documentation covers the basics of how to set this up. Make note of the Topic ARN when you create the topic. -* While not mandatory, it is highly recommended to create a dedicated IAM user on your account for Netdata to send notifications. This user needs to have programmatic access, and should only allow access to SNS. If you're really paranoid, you can create one for each system or group of systems. +- The Amazon Web Services CLI tools. Most distributions provide these with the package name `awscli`. +- An actual home directory for the user you run Netdata as, instead of just using `/` as a home directory. Setup of this is distribution specific. `/var/lib/netdata` is the recommended directory (because the permissions will already be correct) if you are using a dedicated user (which is how most distributions work). +- An Amazon SNS topic to send notifications to with one or more subscribers. The [Getting Started](https://docs.aws.amazon.com/sns/latest/dg/GettingStarted.html) section of the Amazon SNS documentation covers the basics of how to set this up. Make note of the Topic ARN when you create the topic. +- While not mandatory, it is highly recommended to create a dedicated IAM user on your account for Netdata to send notifications. This user needs to have programmatic access, and should only allow access to SNS. If you're really paranoid, you can create one for each system or group of systems. Once you have all the above, run the following command as the user Netdata runs under: - aws configure +``` +aws configure +``` THis will prompt you for the access key and secret key for accessing Amazon SNS (as well as the default region and output format, but you can leave those blank because we don't use them). @@ -26,8 +28,8 @@ Once that's done, you're ready to go and can specify the desired topic ARN as a Notes: - * Netdata's native email notification support is far better in almost all respects than it's support through Amazon SNS. If you want email notifications, use the native support, not SNS. - * If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same vairiables you can use in custom notifications. - * While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality. +- Netdata's native email notification support is far better in almost all respects than it's support through Amazon SNS. If you want email notifications, use the native support, not SNS. + - If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same vairiables you can use in custom notifications. + - While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality. -[]() +[](<>) diff --git a/health/notifications/custom/README.md b/health/notifications/custom/README.md index 80210572b2..18df795419 100644 --- a/health/notifications/custom/README.md +++ b/health/notifications/custom/README.md @@ -39,45 +39,45 @@ The following is a sample `custom_sender` function in `health_alarm_notify.conf` Variables available to the custom_sender: - - `${to_custom}` the list of recipients for the alarm - - `${host}` the host generated this event - - `${url_host}` same as `${host}` but URL encoded - - `${unique_id}` the unique id of this event - - `${alarm_id}` the unique id of the alarm that generated this event - - `${event_id}` the incremental id of the event, for this alarm id - - `${when}` the timestamp this event occurred - - `${name}` the name of the alarm, as given in Netdata health.d entries - - `${url_name}` same as `${name}` but URL encoded - - `${chart}` the name of the chart (type.id) - - `${url_chart}` same as `${chart}` but URL encoded - - `${family}` the family of the chart - - `${url_family}` same as `${family}` but URL encoded - - `${status}` the current status : REMOVED, UNINITIALIZED, UNDEFINED, CLEAR, WARNING, CRITICAL - - `${old_status}` the previous status: REMOVED, UNINITIALIZED, UNDEFINED, CLEAR, WARNING, CRITICAL - - `${value}` the current value of the alarm - - `${old_value}` the previous value of the alarm - - `${src}` the line number and file the alarm has been configured - - `${duration}` the duration in seconds of the previous alarm state - - `${duration_txt}` same as `${duration}` for humans - - `${non_clear_duration}` the total duration in seconds this is/was non-clear - - `${non_clear_duration_txt}` same as `${non_clear_duration}` for humans - - `${units}` the units of the value - - `${info}` a short description of the alarm - - `${value_string}` friendly value (with units) - - `${old_value_string}` friendly old value (with units) - - `${image}` the URL of an image to represent the status of the alarm - - `${color}` a color in #AABBCC format for the alarm - - `${goto_url}` the URL the user can click to see the Netdata dashboard - - `${calc_expression}` the expression evaluated to provide the value for the alarm - - `${calc_param_values}` the value of the variables in the evaluated expression - - `${total_warnings}` the total number of alarms in WARNING state on the host - - `${total_critical}` the total number of alarms in CRITICAL state on the host +- `${to_custom}` the list of recipients for the alarm +- `${host}` the host generated this event +- `${url_host}` same as `${host}` but URL encoded +- `${unique_id}` the unique id of this event +- `${alarm_id}` the unique id of the alarm that generated this event +- `${event_id}` the incremental id of the event, for this alarm id +- `${when}` the timestamp this event occurred +- `${name}` the name of the alarm, as given in Netdata health.d entries +- `${url_name}` same as `${name}` but URL encoded +- `${chart}` the name of the chart (type.id) +- `${url_chart}` same as `${chart}` but URL encoded +- `${family}` the family of the chart +- `${url_family}` same as `${family}` but URL encoded +- `${status}` the current status : REMOVED, UNINITIALIZED, UNDEFINED, CLEAR, WARNING, CRITICAL +- `${old_status}` the previous status: REMOVED, UNINITIALIZED, UNDEFINED, CLEAR, WARNING, CRITICAL +- `${value}` the current value of the alarm +- `${old_value}` the previous value of the alarm +- `${src}` the line number and file the alarm has been configured +- `${duration}` the duration in seconds of the previous alarm state +- `${duration_txt}` same as `${duration}` for humans +- `${non_clear_duration}` the total duration in seconds this is/was non-clear +- `${non_clear_duration_txt}` same as `${non_clear_duration}` for humans +- `${units}` the units of the value +- `${info}` a short description of the alarm +- `${value_string}` friendly value (with units) +- `${old_value_string}` friendly old value (with units) +- `${image}` the URL of an image to represent the status of the alarm +- `${color}` a color in #AABBCC format for the alarm +- `${goto_url}` the URL the user can click to see the Netdata dashboard +- `${calc_expression}` the expression evaluated to provide the value for the alarm +- `${calc_param_values}` the value of the variables in the evaluated expression +- `${total_warnings}` the total number of alarms in WARNING state on the host +- `${total_critical}` the total number of alarms in CRITICAL state on the host The following are more human friendly: - - `${alarm}` like "name = value units" - - `${status_message}` like "needs attention", "recovered", "is critical" - - `${severity}` like "Escalated to CRITICAL", "Recovered from WARNING" - - `${raised_for}` like "(alarm was raised for 10 minutes)" +- `${alarm}` like "name = value units" +- `${status_message}` like "needs attention", "recovered", "is critical" +- `${severity}` like "Escalated to CRITICAL", "Recovered from WARNING" +- `${raised_for}` like "(alarm was raised for 10 minutes)" -[]() +[](<>) diff --git a/health/notifications/discord/README.md b/health/notifications/discord/README.md index 7b43f4e229..88e0a970e3 100644 --- a/health/notifications/discord/README.md +++ b/health/notifications/discord/README.md @@ -6,8 +6,8 @@ This is what you will get: You need: -1. The **incoming webhook URL** as given by Discord. Create a webhook by following the official [Discord documentation](https://support.discordapp.com/hc/en-us/articles/228383668-Intro-to-Webhooks). You can use the same on all your Netdata servers (or you can have multiple if you like - your decision). -2. One or more Discord channels to post the messages to. +1. The **incoming webhook URL** as given by Discord. Create a webhook by following the official [Discord documentation](https://support.discordapp.com/hc/en-us/articles/228383668-Intro-to-Webhooks). You can use the same on all your Netdata servers (or you can have multiple if you like - your decision). +2. One or more Discord channels to post the messages to. Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -29,7 +29,6 @@ DISCORD_WEBHOOK_URL="https://discordapp.com/api/webhooks/XXXXXXXXXXXXX/XXXXXXXXX # this discord channel (empty = do not send a notification for unconfigured # roles): DEFAULT_RECIPIENT_DISCORD="alarms" - ``` You can define multiple channels like this: `alarms systems`. @@ -43,4 +42,4 @@ role_recipients_discord[webmaster]="marketing development" The keywords `systems`, `databases`, `marketing`, `development` are discordapp.com channels (they should already exist within your discord server). -[]() +[](<>) diff --git a/health/notifications/email/README.md b/health/notifications/email/README.md index ebe72f6d86..92916d192a 100644 --- a/health/notifications/email/README.md +++ b/health/notifications/email/README.md @@ -30,6 +30,7 @@ sudo su -s /bin/bash netdata Where `[ROLE]` is the role you want to test. The default (if you don't give a `[ROLE]`) is `sysadmin`. -Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under `/usr/lib/netdata`). You can always find the location of the alarm-notify.sh script in `netdata.conf`. +Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under `/usr/lib/netdata`). +You can always find the location of the alarm-notify.sh script in `netdata.conf`. -[]() +[](<>) diff --git a/health/notifications/flock/README.md b/health/notifications/flock/README.md index 70a850376e..658fc7b828 100644 --- a/health/notifications/flock/README.md +++ b/health/notifications/flock/README.md @@ -2,14 +2,14 @@ This is what you will get: -  You need: -The **incoming webhook URL** as given by flock.com. You can use the same on all your Netdata servers (or you can have multiple if you like - your decision). +The **incoming webhook URL** as given by flock.com. +You can use the same on all your Netdata servers (or you can have multiple if you like - your decision). -Get them here: https://admin.flock.com/webhooks +Get them here: <https://admin.flock.com/webhooks> Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -27,7 +27,6 @@ FLOCK_WEBHOOK_URL="https://api.flock.com/hooks/sendMessage/XXXXXXXXXXXXXXXXXXXXX # if a role recipient is not configured, no notification will be sent DEFAULT_RECIPIENT_FLOCK="alarms" - ``` -[]() +[](<>) diff --git a/health/notifications/irc/README.md b/health/notifications/irc/README.md index 804ff6041b..36590eb79b 100644 --- a/health/notifications/irc/README.md +++ b/health/notifications/irc/README.md @@ -2,15 +2,15 @@ This is what you will get: -IRCCloud web client: +IRCCloud web client:\  Irssi terminal client:  - You need: -1. The `nc` utility. If you do not set the path, Netdata will search for it in your system `$PATH`. + +1. The `nc` utility. If you do not set the path, Netdata will search for it in your system `$PATH`. Set the path for `nc` in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -22,12 +22,11 @@ Set the path for `nc` in `/etc/netdata/health_alarm_notify.conf` (to edit it on # If empty, the system $PATH will be searched for it. # If not found, irc notifications will be silently disabled. nc="/usr/bin/nc" - ``` -2. Αn `IRC_NETWORK` to which your preffered channels belong to. -3. One or more channels ( `DEFAULT_RECIPIENT_IRC` ) to post the messages to. -4. An `IRC_NICKNAME` and an `IRC_REALNAME` to identify in IRC. +2. Αn `IRC_NETWORK` to which your preffered channels belong to. +3. One or more channels ( `DEFAULT_RECIPIENT_IRC` ) to post the messages to. +4. An `IRC_NICKNAME` and an `IRC_REALNAME` to identify in IRC. Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -57,11 +56,10 @@ IRC_NICKNAME="netdata-alarm-user" # The irc realname which is required in order to make the connection and is an # extra identifier. IRC_REALNAME="netdata-user" - ``` -You can define multiple channels like this: `#system-alarms #networking-alarms`. -You can also filter the notifications like this: `#system-alarms|critical`. +You can define multiple channels like this: `#system-alarms #networking-alarms`.\ +You can also filter the notifications like this: `#system-alarms|critical`.\ You can give different channels per **role** using these (at the same file): ``` @@ -72,4 +70,4 @@ role_recipients_irc[webmaster]="#networking-alarms" The keywords `#user-alarms`, `#networking-alarms`, `#system-alarms`, `#databases-alarms` are irc channels which belong to the specified IRC network. -[]() +[](<>) diff --git a/health/notifications/kavenegar/README.md b/health/notifications/kavenegar/README.md index b8026b89a4..495b5338eb 100644 --- a/health/notifications/kavenegar/README.md +++ b/health/notifications/kavenegar/README.md @@ -8,10 +8,10 @@ Will look like this on your Android device: You will need: -1. Signup and Login to kavenegar.com -2. Get your APIKEY and Sender from http://panel.kavenegar.com/client/setting/account -3. Fill in KAVENEGAR_API_KEY="" KAVENEGAR_SENDER="" -4. Add the recipient phone numbers to DEFAULT_RECIPIENT_KAVENEGAR="" +1. Signup and Login to kavenegar.com +2. Get your APIKEY and Sender from <http://panel.kavenegar.com/client/setting/account> +3. Fill in KAVENEGAR_API_KEY="" KAVENEGAR_SENDER="" +4. Add the recipient phone numbers to DEFAULT_RECIPIENT_KAVENEGAR="" Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -38,4 +38,4 @@ KAVENEGAR_SENDER="" DEFAULT_RECIPIENT_KAVENEGAR="" ``` -[]() +[](<>) diff --git a/health/notifications/messagebird/README.md b/health/notifications/messagebird/README.md index 62b8b2eaa3..30d52a4f27 100644 --- a/health/notifications/messagebird/README.md +++ b/health/notifications/messagebird/README.md @@ -6,12 +6,12 @@ The messagebird notifications will look like this on your Android device: You will need: -1. Signup and Login to messagebird.com -2. Pick an SMS capable number after sign up to get some free credits -3. Go to <https://www.messagebird.com/app/settings/developers/access> -4. Create a new access key under 'API ACCESS (REST)' (you will want a live key) -3. Fill in MESSAGEBIRD_ACCESS_KEY="XXXXXXXX" MESSAGEBIRD_NUMBER="+XXXXXXXXXXX" -4. Add the recipient phone numbers to DEFAULT_RECIPIENT_MESSAGEBIRD="+XXXXXXXXXXX" +1. Signup and Login to messagebird.com +2. Pick an SMS capable number after sign up to get some free credits +3. Go to <https://www.messagebird.com/app/settings/developers/access> +4. Create a new access key under 'API ACCESS (REST)' (you will want a live key) +5. Fill in MESSAGEBIRD_ACCESS_KEY="XXXXXXXX" MESSAGEBIRD_NUMBER="+XXXXXXXXXXX" +6. Add the recipient phone numbers to DEFAULT_RECIPIENT_MESSAGEBIRD="+XXXXXXXXXXX" Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -35,7 +35,6 @@ SEND_MESSAGEBIRD="YES" MESSAGEBIRD_ACCESS_KEY="XXXXXXXX" MESSAGEBIRD_NUMBER="XXXXXXX" DEFAULT_RECIPIENT_MESSAGEBIRD="XXXXXXX" - ``` -[]() +[](<>) diff --git a/health/notifications/pagerduty/README.md b/health/notifications/pagerduty/README.md index 8f03a0695e..59a48515ce 100644 --- a/health/notifications/pagerduty/README.md +++ b/health/notifications/pagerduty/README.md @@ -8,7 +8,7 @@ Here is an example of a PagerDuty dashboard with Netdata notifications: To have Netdata send notifications to PagerDuty, you'll first need to set up a PagerDuty `Generic API` service and install the PagerDuty agent on the host running Netdata. See the following guide for details: -https://www.pagerduty.com/docs/guides/agent-install-guide/ +<https://www.pagerduty.com/docs/guides/agent-install-guide/> During the setup of the `Generic API` PagerDuty service, you'll obtain a `pagerduty service key`. Keep this **service key** handy. @@ -34,4 +34,4 @@ SEND_PD="YES" DEFAULT_RECIPIENT_PD="<service key>" ``` -[]() +[](<>) diff --git a/health/notifications/pushbullet/README.md b/health/notifications/pushbullet/README.md index 0c0b9a3224..f5673eca9f 100644 --- a/health/notifications/pushbullet/README.md +++ b/health/notifications/pushbullet/README.md @@ -5,16 +5,15 @@ Will look like this on your browser: And like this on your Android device: -  You will need: -1. Signup and Login to pushbullet.com -2. Get your Access Token, go to https://www.pushbullet.com/#settings/account and create a new one -3. Fill in the PUSHBULLET_ACCESS_TOKEN with that value -4. Add the recipient emails to DEFAULT_RECIPIENT_PUSHBULLET -!!PLEASE NOTE THAT IF THE RECIPIENT DOES NOT HAVE A PUSHBULLET ACCOUNT, PUSHBULLET SERVICE WILL SEND AN EMAIL!! +1. Signup and Login to pushbullet.com +2. Get your Access Token, go to <https://www.pushbullet.com/#settings/account> and create a new one +3. Fill in the PUSHBULLET_ACCESS_TOKEN with that value +4. Add the recipient emails to DEFAULT_RECIPIENT_PUSHBULLET + !!PLEASE NOTE THAT IF THE RECIPIENT DOES NOT HAVE A PUSHBULLET ACCOUNT, PUSHBULLET SERVICE WILL SEND AN EMAIL!! Set them in `/etc/netdata/health_alarm_notify.conf` (to edit it on your system run `/etc/netdata/edit-config health_alarm_notify.conf`), like this: @@ -41,4 +40,4 @@ PUSHBULLET_ACCESS_TOKEN="o.Sometokenhere" DEFAULT_RECIPIENT_PUSHBULLET="admin1@example.com admin3@somemail.com" ``` -[]() +[](<>) diff --git a/health/notifications/pushover/README.md b/health/notifications/pushover/README.md index 90e2646a9b..2d488d1a8c 100644 --- a/ |