InfluxDB 3 Core
InfluxDB 3
InfluxDB 2
Other products
This page has moved to InfluxDB HTTP API.
Was this page helpful?
Thank you for your feedback!
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB 3 Core and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.
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:
Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.
Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.
Highlights:
For more details, see Explorer 1.9 release notes
Key updates in InfluxDB 3 Core 3.10:
--max-concurrent-queries: limit concurrent queries (adjustable at runtime).GET /ready endpoint for readiness probes.For more information, see the InfluxDB 3 Core release notes.
Key updates in InfluxDB 3 Enterprise 3.10:
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 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.
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