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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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