Create notification rules

Once you’ve set up checks and notification endpoints, create notification rules to alert you. For details, see Manage checks and Manage notification endpoints.

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

  2. Select Notification Rules near to top of the page.

Create a new notification rule

  1. On the notification rules page, click Create.
  2. Complete the About section:
  3. In the Name field, enter a name for the notification rule.
  4. In the Schedule Every field, enter how frequently the rule should run.
  5. In the Offset field, enter an offset time. For example,if a task runs on the hour, a 10m offset delays the task to 10 minutes after the hour. Time ranges defined in the task are relative to the specified execution time.
  6. In the Conditions section, build a condition using a combination of status and tag keys.
    • Next to When status is equal to, select a status from the drop-down field.
    • Next to AND When, enter one or more tag key-value pairs to filter by.
  7. In the Message section, select an endpoint to notify.
  8. Click Create Notification Rule.

Clone an existing notification rule

On the notification rules page, click the icon and select Clone. The cloned rule appears.

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless 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.