Documentation

influxctl database rename

The influxctl database rename command renames a database in an InfluxDB cluster. This command does not change the database ID, database properties, or the data stored in the database.

Renaming a database requires new tokens

Database tokens are associated to databases by name. After renaming a database, tokens referencing the old name no longer function. You must generate tokens for the new database name.

Usage

influxctl database rename [flags] <CURRENT_DB_NAME> <NEW_DB_NAME>

Arguments

ArgumentDescription
CURRENT_DB_NAMECurrent name of the database
NEW_DB_NAMENew name for the database

Flags

FlagDescription
-h--helpOutput command help

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