Documentation

InfluxDB file system layout

The InfluxDB Enterprise file system layout depends on the installation method or containerization platform used to install InfluxDB Enterprise.

InfluxDB Enterprise file structure

The InfluxDB file structure includes the following:

Data directory

(Data nodes only) Directory path where InfluxDB Enterprise stores time series data (TSM files). To customize this path, use the [data].dir configuration option.

WAL directory

(Data nodes only) Directory path where InfluxDB Enterprise stores Write Ahead Log (WAL) files. To customize this path, use the [data].wal-dir configuration option.

Hinted handoff directory

(Data nodes only) Directory path where hinted handoff (HH) queues are stored. To customize this path, use the [hinted-handoff].dir configuration option.

Metastore directory

Directory path of the InfluxDB Enterprise metastore, which stores information about the cluster, users, databases, retention policies, shards, and continuous queries.

On data nodes, the metastore contains information about InfluxDB Enterprise meta nodes. To customize this path, use the [meta].dir configuration option in your data node configuration file.

On meta nodes, the metastore contains information about the InfluxDB Enterprise RAFT cluster. To customize this path, use the [meta].dir configuration option in your meta node configuration file.

InfluxDB Enterprise configuration files

InfluxDB Enterprise stores default data and meta node configuration file on disk. For more information about using InfluxDB Enterprise configuration files, see:

File system layout

InfluxDB Enterprise supports .deb- and .rpm-based Linux package managers. The file system layout is the same with each.

Data node file system layout

PathDefault
Data directory/var/lib/influxdb/data/
WAL directory/var/lib/influxdb/wal/
Metastore directory/var/lib/influxdb/meta/
Hinted handoff directory/var/lib/influxdb/hh/
Default config file path/etc/influxdb/influxdb.conf
Data node file system overview
  • /etc/influxdb/
    • influxdb.conf (Data node configuration file)
  • /var/lib/influxdb/
    • data/
      • TSM directories and files
    • hh/
      • HH queue files
    • meta/
      • client.json
    • wal/
      • WAL directories and files

Meta node file system layout

PathDefault
Metastore directory/var/lib/influxdb/meta/
Default config file path/etc/influxdb/influxdb-meta.conf
Meta node file system overview
  • /etc/influxdb/
    • influxdb-meta.conf (Meta node configuration file)
  • /var/lib/influxdb/
    • meta/
      • peers.json
      • raft.db
      • snapshots/
        • Snapshot directories and files

Directory permissions

The user running the influxd process should have the following permissions for directories in the InfluxDB file system:

Directory pathPermission
.../influxdb/755
.../influxdb/data/755
.../influxdb/hh/700
.../influxdb/meta/755
.../influxdb/wal/700

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.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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 May 27, 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