Delete data

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

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

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.

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

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

See the Blog Post

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: