Documentation

InfluxDB OSS v2

influxd inspect report-tsm

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

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.

Usage

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.

Flags

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
tsm cardinality inspect

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB OSS URL?

Customize your InfluxDB OSS URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

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