Documentation

Update notification endpoints

Complete the following steps to update notification endpoint details. To update the notification endpoint selected for a notification rule, see update notification rules.

To update a notification endpoint

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

  2. Select Notification Endpoints and then do the following as needed:

Update the name or description for notification endpoint

  1. Hover over the name or description of the endpoint and click the pencil icon () to edit the field.
  2. Click outside of the field to save your changes.

Change endpoint details

  1. Click the name of the endpoint to update.
  2. Update details as needed, and then click Edit Notification Endpoint. For details about each field, see Create notification endpoints.

Disable notification endpoint

Click the toggle to disable the notification endpoint.

Add a label to notification endpoint

  1. Click Add a label next to the endpoint you want to add a label to. The Add Labels box opens.

  2. To add an existing label, select the label from the list.

  3. To create and add a new label:

    • In the search field, enter the name of the new label. The Create Label box opens.
    • In the Description field, enter an optional description for the label.
    • Select a color for the label.
    • Click Create Label.
  4. To remove a label, click on the label.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: