Documentation

InfluxDB OSS v2

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
buckets

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

What is your InfluxDB OSS URL?

Customize your InfluxDB OSS URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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