InfluxDB 3 Enterprise
InfluxDB 3
InfluxDB 2
Other products
Configure a standalone process node, a node that runs only the Processing Engine, in an InfluxDB 3 Enterprise cluster: plan the cluster, start the nodes, create triggers, send each request to the right node, and troubleshoot common errors.
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.Run Telegraf Controller in Docker
Release notes
Read the announcement
InfluxDB OSS 1.13.1 adds mTLS support, adaptive TSI cache sizing, and a hardening option to mitigate SSRF.
Key updates in InfluxDB OSS 1.13.1:
hardening-enabled option to mitigate server-side request
forgery (SSRF) in Flux HTTP requests.For details, see the InfluxDB OSS 1.13.1 release notes.
InfluxDB Enterprise 1.13.1 adds mTLS support and includes the InfluxDB OSS 1.13.1 updates.
Key updates in InfluxDB Enterprise 1.13.1:
For details, see the InfluxDB Enterprise 1.13.1 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