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!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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