Documentation

InfluxDB Enterprise v1 features

InfluxDB Enterprise has additional capabilities that enhance availability, scalability, and security, and provide eventual consistency.

Clustering

InfluxDB Enterprise runs on a network of independent servers, a cluster, to provide fault tolerance, availability, and horizontal scalability of the database.

While many InfluxDB Enterprise features are available when run with a single meta node and a single data node, this configuration does not take advantage of the clustering capability or ensure high availability.

Nodes can be added to an existing cluster to improve database performance for querying and writing data. Certain configurations (e.g., 3 meta and 2 data node) provide high-availability assurances while making certain tradeoffs in query performance when compared to a single node.

Further increasing the number of nodes can improve performance in both respects. For example, a cluster with 4 data nodes and a replication factor of 2 can support a higher volume of write traffic than a single node could. It can also support a higher query workload, as the data is replicated in two locations. Performance of the queries may be on par with a single node in cases where the query can be answered directly by the node which receives the query.

For more information on clustering, see Clustering in InfluxDB Enterprise.

Security

Enterprise authorization uses an expanded set of 16 user permissions and roles. (InfluxDB OSS only has READ and WRITE permissions.) Administrators can give users permission to read and write to databases, create and remove databases, rebalance a cluster, and manage particular resources.

Organizations can automate managing permissions with the InfluxDB Enterprise Meta API.

Fine-grained authorization for particular data is also available.

InfluxDB Enterprise can also use LDAP for managing authentication.

For FIPS compliance, InfluxDB Enterprise password hashing algorithms are configurable.

Kapacitor OSS can also delegate its LDAP and security setup to InfluxDB Enterprise. For details, see “Set up InfluxDB Enterprise authorizations”.

Eventual consistency

Hinted handoff

Hinted handoff (HH) is how InfluxDB Enterprise deals with data node outages while writes are happening. HH is essentially a durable disk based queue.

For more information, see “Hinted handoff”.

Anti-entropy

Anti-entropy is an optional service to eliminate edge cases related to cluster consistency.

For more information, see “Use Anti-Entropy service in InfluxDB Enterprise”.



Was this page helpful?

Thank you for your feedback!


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

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

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 now in public beta

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

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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