Documentation

influxd inspect dump-wal

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

The influxd inspect dump-wal command outputs data from Write Ahead Log (WAL) files for debugging purposes. Given at least one WAL file path as an argument, the tool parses and prints out the entries in each file.

Usage

influxd inspect dump-wal [flags]

Output details

The --find-duplicates flag determines the influxd inspect dump-wal output.

Without --find-duplicates, the command outputs the following for each file:

  • The file name
  • For each entry in a file: - The type of the entry ([write] or [delete-bucket-range]) - The formatted entry contents

With --find-duplicates, the command outputs the following for each file):

  • The file name
  • A list of keys with timestamps in the wrong order

Flags

FlagDescription
--find-duplicatesIgnore dumping entries; only report keys in the WAL that are out of order.
-h--helpHelp for the dump-wal 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