Documentation

influxd inspect report-db

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The influxd inspect report-db command analyzes an InfluxDB bucket and reports the cardinality of data stored in the bucket.

Usage

influxd inspect report-db [flags]

Flags

FlagDescriptionInput Type
--cWorker concurrency (default is 1).integer
--db-path(Required) Path to InfluxDB data directory.string
--detailedInclude field and tag counts in output.
--exactReport exact counts.
-h--helpView help for the report-db command.
--rollupRollup level: t (total), b (bucket), r (retention policy), or m (measurement) (default).string

Examples

Report the cardinality of measurements in all buckets

# Syntax
influxd inspect report-db --db-path <influxdb-data-directory>

# Example
influxd inspect report-db --db-path ~/.influxdbv2/engine/data

Report the cardinality of measurements in a specific bucket

# Syntax
influxd inspect report-db --db-path <influxdb-data-directory>/<bucket-id>

# Example
influxd inspect report-db --db-path ~/.influxdbv2/engine/data/000xX00xxXx000x0

Report the cardinality of all buckets

  • Use the --db-path flag to provide the path to your InfluxDB data directory.
  • Use the --rollup flag with the value, b, to return a bucket-level summary of cardinality.
# Syntax
influxd inspect report-db \
  --db-path <influxdb-data-directory> \
  --rollup b

# Example
influxd inspect report-db \
  --db-path ~/.influxdbv2/engine/data \
  --rollup b

Report the cardinality of all retention policies

  • Use the --db-path flag to provide the path to your InfluxDB data directory.
  • Use the --rollup flag with the value, r, to return a retention-policy-level summary of cardinality.
# Syntax
influxd inspect report-db \
  --db-path <influxdb-data-directory> \
  --rollup r

# Example
influxd inspect report-db \
  --db-path ~/.influxdbv2/engine/data \
  --rollup r

Report the total cardinality of your InfluxDB instance

  • Use the --db-path flag to provide the path to your InfluxDB data directory.
  • Use the --rollup flag with the value, t, to return a summary of total cardinality.
# Syntax
influxd inspect report-db \
  --db-path <influxdb-data-directory> \
  --rollup t

# Example
influxd inspect report-db \
  --db-path ~/.influxdbv2/engine/data \
  --rollup t

Include tag and field counts in your cardinality summary

  • Use the --db-path flag to provide the path to your InfluxDB data directory.
  • Include the --detailed flag to return detailed cardinality summaries with tag and field counts.
# Syntax
influxd inspect report-db \
  --db-path <influxdb-data-directory> \
  --detailed

# Example
influxd inspect report-db \
  --db-path ~/.influxdbv2/engine/data \
  --detailed

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

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