Documentation

influxd inspect

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

The influxd inspect commands and subcommands inspecting on-disk InfluxDB time series data.

Usage

influxd inspect [subcommand]

Subcommands

SubcommandDescription
build-tsiRebuild the TSI index and series file
check-schemaCheck for conflicts between shard types
delete-tsmDelete a measurement from a TSM file
dump-tsiOutput low level TSI information
dump-tsmOutput low level TSM information
dump-walOutput TSM data from WAL files
export-indexExport TSI index data
export-lpExport TSM data to line protocol
merge-schemaMerge a set of schema files
report-dbReport the cardinality of a bucket
report-tsiReport the cardinality of TSI files
report-tsmReport information about TSM files
verify-seriesfileVerify the integrity of series files
verify-tombstoneVerify the integrity of tombstone files
verify-tsmVerify the integrity of TSM files
verify-walVerify the integrity of WAL files

Flags

FlagDescription
-h--helpHelp for the inspect command

Was this page helpful?

Thank you for your feedback!


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 November 3, 2025, 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