Documentation

influxd inspect report-db

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

Flag Description Input Type
--c Worker concurrency (default is 1). integer
--db-path (Required) Path to InfluxDB data directory. string
--detailed Include field and tag counts in output.
--exact Report exact counts.
-h --help View help for the report-db command.
--rollup Rollup 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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.