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!


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: