influxd inspect report-tsm

The influxd inspect report-tsm command analyzes Time-Structured Merge Tree (TSM) files within a storage engine directory and reports the cardinality within the files and the time range the data covers.

This command only reports on the index within each TSM file. It does not read any block data. To reduce heap requirements, by default report-tsm estimates the overall cardinality in the file set by using the HLL++ algorithm. Determine exact cardinalities by using the --exact flag.


influxd inspect report-tsm [flags]

Output details

influxd inspect report-tsm outputs the following for each TSM file:

  • The full file name.
  • The series cardinality within the file.
  • The number of series first encountered within the file.
  • The minimum and maximum timestamp associated with TSM data in the file.
  • The time to load the TSM index and apply any tombstones.

The summary section then outputs the total time range and series cardinality for the file set. Depending on the --detailed flag, series cardinality is segmented in the following ways:

  • Series cardinality for each organization.
  • Series cardinality for each bucket.
  • Series cardinality for each measurement.
  • Number of field keys for each measurement.
  • Number of tag values for each tag key.


FlagDescriptionInput Type
--data-pathPath to data directory (defaults to ~/.influxdbv2/engine/data).string
--detailedEmit series cardinality segmented by measurements, tag keys, and fields. May take a while.
--exactCalculate an exact cardinality count. May use significant memory.
-h--helpHelp for the report-tsm command.
--patternOnly process TSM files containing pattern.string

Was this page helpful?

Thank you for your feedback!

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: