Create notification endpoints
To send notifications about changes in your data, start by creating a notification endpoint to a third-party service. After creating notification endpoints, create notification rules to send alerts to third-party services on check statuses.
Create a notification endpoint in the UI
In the navigation menu on the left, select Alerts.
Select Notification Endpoints near to top of the page.
From the Destination drop-down list, select a destination endpoint to send notifications
In the Name and Description fields, enter a name and description for the endpoint.
Enter information to connect to the endpoint:
For HTTP, enter the URL to send the notification. Select the auth method to use: None for no authentication. To authenticate with a username and password, select Basic and then enter credentials in the Username and Password fields. To authenticate with an API token, select Bearer, and then enter the API token in the Token field.
For Slack, create an Incoming WebHook in Slack, and then enter your webHook URL in the Slack Incoming WebHook URL field.
The Client URL provides a useful link in your PagerDuty notification. Enter any URL that you’d like to use to investigate issues. This URL is sent as the
client_urlproperty in the PagerDuty trigger event. By default, the Client URL is set to your Monitoring & Alerting History page, and the following included in the PagerDuty trigger event:
Click Create Notification Endpoint.
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.