InfluxDB 3 Enterprise
InfluxDB 3
InfluxDB 2
Other products
Learn how InfluxDB 3 Enterprise finds and deletes compacted files that nothing references, when cleanup passes run, and how to inspect cleanup activity with the influxdb3 debug sweep and influxdb3 debug verify-references commands.
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.
Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.
Also new in 2.9.0:
EXPLAIN and EXPLAIN ANALYZE in the SQL editor.influxdb3 update table.--max-concurrent-queries and an enforced
WAL buffer limit.Telegraf Controller 1.1 lets teams make fleet-wide configuration changes with a single edit using global constants, configuration groups, and configuration aliases. Configuration versioning makes every change traceable, comparable, and reversible. High availability, available with Telegraf Enterprise, automatically fails over between Controller instances so agents can continue pulling configurations and reporting health if an instance goes down.
InfluxDB OSS 1.13.0 adds mTLS support, adaptive TSI cache sizing, and a hardening option to mitigate SSRF.
Key updates in InfluxDB OSS 1.13.0:
hardening-enabled option to mitigate server-side request
forgery (SSRF) in Flux HTTP requests.For details, see the InfluxDB OSS 1.13.0 release notes.
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