InfluxDB Docs

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

  1. Select the Monitoring and Alerting icon from the sidebar.

  2. Next to Notification Endpoints, click Create.

  3. From the Destination drop-down list, select a destination endpoint to send notifications. The following endpoints are available for InfluxDB 2.0 OSS, the InfluxDB Cloud 2.0 Free Plan, and the InfluxDB Cloud 2.0 Usage-based Plan:

    EndpointOSSFree Plan (Cloud)Usage-based Plan (Cloud)
  4. In the Name and Description fields, enter a name and description for the endpoint.

  5. Enter 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 a token, select Bearer, and then enter the authentication 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.

    • For PagerDuty:

      • Create a new service, add an integration for your service, and then enter the PagerDuty integration key for your new service in the Routing Key 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_url property 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: "client_url": "<your-org-ID>/alert-history”
  6. Click Create Notification Endpoint.