Documentation

monitor package

The monitor package provides tools for monitoring and alerting with InfluxDB. Import the influxdata/influxdb/monitor package:

import "influxdata/influxdb/monitor"

Constants

monitor.bucket = "_monitoring"
monitor.levelCrit = "crit"
monitor.levelInfo = "info"
monitor.levelOK = "ok"
monitor.levelUnknown = "unknown"
monitor.levelWarn = "warn"
  • monitor.bucket is the default bucket to store InfluxDB monitoring data in.
  • monitor.levelCrit is the string representation of the “crit” level.
  • monitor.levelInfo is the string representation of the “info” level.
  • monitor.levelOK is the string representation of the “ok” level.
  • monitor.levelUnknown is the string representation of the an unknown level.
  • monitor.levelWarn is the string representation of the “warn” level.

Options

option monitor.log = (tables=<-) => tables |> experimental.to(bucket: bucket)

option monitor.write = (tables=<-) => tables |> experimental.to(bucket: bucket)

log

log persists notification events to an InfluxDB bucket.

write

write persists check statuses to an InfluxDB bucket.

Functions


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2