Documentation

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.

Endpoints available in InfluxDB Cloud

The following endpoints are available for the InfluxDB Cloud Free Plan and Usage-based Plan:

EndpointFree PlanUsage-based Plan
Slack
PagerDuty
HTTP

Create a notification endpoint

  1. In the navigation menu on the left, select Alerts > Alerts.

  2. Select Notification Endpoints.

  3. Click Create.

  4. From the Destination drop-down list, select a destination endpoint to send notifications to. See available endpoints.

  5. In the Name and Description fields, enter a name and description for the endpoint.

  6. 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.

    • 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": "http://localhost:8086/orgs/<your-org-ID>/alert-history"
        
  7. Click Create Notification Endpoint.


Was this page helpful?

Thank you for your feedback!


Select your region

Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.