Documentation

Delete a custom file index

Use the influxdb3 delete file_index command to delete a custom file indexing strategy from a database or a table and revert to the default indexing strategy.

Provide the following:

  • Token (--token): (Required) Your admin token . You can also use the INFLUXDB3_AUTH_TOKEN environment variable to specify the token.
  • Database (-d, --database): (Required) The name of the database to apply remove the custom index from. You can also use the INFLUXDB3_DATABASE_NAME environment variable to specify the database.
  • Table (-t, --table): The name of the table to remove the custom index from. If no table is specified, the custom indexing strategy is removed from all tables in the specified database.
influxdb3 delete file_index \
  --host http://localhost:8585 \
  --database 
DATABASE
_NAME \
--table
TABLE
_NAME \

Replace the following placeholders with your values:

  • AUTH_TOKEN: your admin token

  • DATABASE_NAME: the name of the database to remove the custom file index from

  • TABLE_NAME: the name of the table to remove the custom file index from


Was this page helpful?

Thank you for your feedback!


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.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-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