Documentation

influxdb3 delete

The influxdb3 delete command deletes a resource such as a cache, a database, or a table.

Usage

influxdb3 delete <SUBCOMMAND>

Subcommands

SubcommandDescription
databaseDelete a database
file_indexDelete a file index for a database or table
last_cacheDelete a last value cache
distinct_cacheDelete a metadata cache
tableDelete a table from a database
tokenDelete an authorization token from the server
triggerDelete a trigger for the processing engine
helpPrint command help or the help of a subcommand

Options

OptionDescription
-h--helpPrint help information
--help-allPrint detailed help information

Was this page helpful?

Thank you for your feedback!


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:

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