Documentation

influxdb3 show retention

The influxdb3 show retention command displays effective retention periods for tables in your InfluxDB 3 Core server.

Usage

influxdb3 show retention [OPTIONS]

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Core server (default is http://127.0.0.1:8181)
--token(Required) Authentication token
--databaseFilter retention information by database name
--formatOutput format (pretty (default), json, jsonl, csv, or parquet)
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token

Examples

Show retention for all tables

influxdb3 show retention \
  --host http://localhost:8181 \
  --token YOUR_AUTH_TOKEN

Show retention for a specific database

influxdb3 show retention \
  --host http://localhost:8181 \
  --token YOUR_AUTH_TOKEN \
  --database mydb

Show retention in JSON format

influxdb3 show retention \
  --host http://localhost:8181 \
  --token YOUR_AUTH_TOKEN \
  --format json

Output

The command displays the following information for each table:

  • Database: The database name
  • Table: The table name
  • Retention: The effective retention period in human-readable format (for example, “7d” for 7 days, “24h” for 24 hours, “infinite” for no retention)
  • Source: Where the retention is defined (table, database, or infinite)

Example output

Database | Table       | Retention | Source
---------|-------------|-----------|----------
mydb     | cpu         | 7d        | database
mydb     | mem         | 24h       | table
mydb     | disk        | infinite  | infinite

Tables with table-level retention policies override the database-level retention. Tables without explicit retention policies inherit the database retention or have infinite retention if none is set.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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