Documentation

InfluxDB system buckets

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

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.

InfluxDB system buckets contain time series data used by and generated from the InfluxDB monitoring and alerting system and the task engine.

Each InfluxDB organization includes the following system buckets:

The system bucket schemas below reference InfluxDB data elements. For more information, see InfluxDB key concepts.

_monitoring system bucket

The _monitoring system bucket stores InfluxDB data used to monitor data and send alerts.

Data retention: 7 days

_monitoring bucket schema

  • statuses (measurement)
    • tags:
      • _check_id: check ID
      • _check_name: check name
      • _level: level evaluated by the check (ok, info, warn, or crit)
      • _source_measurement: original measurement queried by the check
      • _type: check type (threshold or deadman)
      • other tags inherited from queried data or added in the check configuration
    • fields:
      • _message: message generated by the check
      • _source_timestamp: original timestamp of the queried data
      • other fields inherited from queried data
  • notifications (measurement)
    • tags:
      • _check_id: check ID that triggered the notification
      • _check_name: check name that triggered the notification
      • _level: check-evaluated level that triggered the notification (ok, info, warn, or crit)
      • _notification_endpoint_id: notification endpoint ID
      • _notification_endpoint_name: notification endpoint name
      • _notification_rule_id: notification rule ID
      • _notification_rule_name: notification rule name
      • _sent: sent status (true or false)
      • _source_measurement: original measurement queried by the check
      • _type: check type (threshold or deadman)
      • other tags inherited from queried data or added in the check configuration
    • fields:
      • _message: message generated by the check
      • _source_timestamp: original timestamp of the queried data
      • _status_timestamp: timestamp when the status (_level) was evaluated
      • other fields inherited from queried data

_tasks system bucket

The _tasks system bucket stores data related to InfluxDB task executions.

Data retention: 3 days

_tasks bucket schema

A task run refers to a single task execution.

  • runs (measurement)
    • tags:
      • status: task run status (success or failed)
      • taskID: task ID
    • fields:
      • finishedAt: timestamp when the task run finished
      • logs: log output from the task run
      • requestedAt: timestamp when the task run was requested
      • runID task run ID
      • scheduledFor: timestamp the task run was scheduled for
      • startedAt: timestamp when the task run started

Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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