Monitor data and send alerts

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

Monitor your time series data and send alerts by creating checks, notification rules, and notification endpoints. Or use community templates to monitor supported environments.

Overview

  1. A check in InfluxDB queries data and assigns a status with a _level based on specific conditions.
  2. InfluxDB stores the output of a check in the statuses measurement in the _monitoring system bucket.
  3. Notification rules check data in the statuses measurement and, based on conditions set in the notification rule, send a message to a notification endpoint.
  4. InfluxDB stores notifications in the notifications measurement in the _monitoring system bucket.

Create an alert

To get started, do the following:

  1. Create checks to monitor data and assign a status.
  2. Add notification endpoints to send notifications to third parties.
  3. Create notification rules to check statuses and send notifications to your notifications endpoints.

Manage your monitoring and alerting pipeline

Manage checks

Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.

Manage notification endpoints

Create, read, update, and delete endpoints in the InfluxDB UI.

Manage notification rules

Manage notification rules in InfluxDB.

Monitor with templates

Use community templates to monitor data in many supported environments. Monitor infrastructure, networking, IoT, software, security, TICK stack, and more.

Send alert email

Send an alert email.

Create custom checks

Create custom checks with a Flux task.

Was this page helpful?

Thank you for your feedback!