Documentation

influxd inspect

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

Usage

influxd inspect [subcommand]

Subcommands

Subcommand Description
build-tsi Rebuild the TSI index and series file
check-schema Check for conflicts between shard types
delete-tsm Delete a measurement from a TSM file
dump-tsi Output low level TSI information
dump-tsm Output low level TSM information
dump-wal Output TSM data from WAL files
export-index Export TSI index data
export-lp Export TSM data to line protocol
merge-schema Merge a set of schema files
report-db Report the cardinality of a bucket
report-tsi Report the cardinality of TSI files
report-tsm Report information about TSM files
verify-seriesfile Verify the integrity of series files
verify-tombstone Verify the integrity of tombstone files
verify-tsm Verify the integrity of TSM files
verify-wal Verify the integrity of WAL files

Flags

Flag Description
-h --help Help for the inspect command

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: