You first create a notifier list containing details about the stakeholders or systems to which you want to send alerts, and then you attach the notifier list to an alert or monitoring job.
Before you begin
- Make sure that your user or team permissions are set to manage notifier lists.
- Monitoring jobs rely on notifier lists to facilitate automatic updates to answer metadata as part of an automatic failover configuration. The notifier list attached to a monitoring job must have the Enable NS1 monitoring data feeds option enabled to facilitate these updates. If using the API, this is achieved by adding the data feed notifier to the list.
- Make sure that you have the following information for the stakeholders and systems that you want to add to this notifier list.
| Notification channel |
Contact details of stakeholder or system |
| Email |
Email address |
| PagerDuty |
PagerDuty integration key |
| Slack |
- Slackbot username
- Webhook URL
- Slack channel or username
|
| Webhook |
Webhook URL |
About this task
You can create a list of notifiers when you create or edit an alert. You can also create the list outside of the alert. You can use whichever method is more convenient for you. The following instructions describe both methods, but if you want to create a notifier list when you create or edit an alert, start at Step 3.
When you create a notifier list, you have the option of selecting existing notifiers or creating a new notifier. Any notifiers that were created for other lists, including those for monitoring alerts, are available for you to choose from. You can create multiple notifiers.
Procedure
-
Click Alerts.
-
Click the Notifier lists tab.
-
Click Create notifier list.
-
In Name, enter a unique name to describe the notifier list.
Do not include special characters.
-
In Notifier(s), select or create the notifier for the stakeholder or system that you want to send notifications to:
- From the drop-down list, select the existing stakeholder or system to include in the list.
- To create a new stakeholder or system, click Create notifier.
-
If you chose Create notifier, configure how to send the notification and to which stakeholder or system:
| To send an alert through... | ...complete these steps... |
|---|
| Email |
- From the Notifier type drop-down list, select Email.
- In Email address, enter the email address of the stakeholder.
- Click Create notifier.
|
| PagerDuty |
- From the Notifier type drop-down list, select PagerDuty.
- In PagerDuty key, enter the integration key that was generated from PagerDuty.
- Click Create notifier.
|
| Slack |
- From the Notifier type drop-down list, select Slack.
- In Slackbot username, enter the name of the notification bot in Slack.
- In Webhook URL, enter the URL generated in Slack where IBM® NS1 Connect® can send alerts to.
- In Slack channel/user, enter the Slack channel or the username that NS1 Connect can send alerts to. Be sure to include the @ or # symbol.
- Click Create notifier.
|
| Webhook |
- From the Notifier type drop-down list, select Webhook.
- In Webhook URL, enter the URL where NS1 Connect can send alerts through.
- To add webhook headers, click Add header and enter the key and value for each webhook.
- Click Create notifier.
|
-
To create more notifiers, click Create notifier and repeat Step 6.
-
Select the Enable NS1 monitoring data feeds check box to ensure any monitoring jobs associated with this notifier list can automatically update the status of the answers corresponding to the monitored endpoint. Enabling this option adds an NS1 Monitoring Data Feed notifier to the notifier list.
Attention: If you don't enable NS1 Connect monitoring data feeds in the notifier list settings, any monitoring jobs associated with the list can't update the up/down status of connected answers. This could break your automatic failover configurations.
-
Click Create notifier list.
What to do next
- Attach the notifier list to an alert when creating or editing an alert.
- Add the notifier list to a monitoring job to facilitate automatic updates to corresponding answer metadata.