Documentation

influxd inspect export-lp

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

The influxd inspect export-lp command exports all time-structured merge tree (TSM) data in a bucket to line protocol.

Usage

influxd inspect export-lp [flags]

Flags

FlagDescriptionInput type
--bucket-id(Required) Bucket IDstring
--compressCompress output with gzip
--endEnd time to export (RFC3339 format)string
--engine-path(Required) Path to persistent InfluxDB engine filesstring
-h--helpHelp for the export-lp command.
--log-levelLog-level (debug, info (default), or error)string
--measurementMeasurement name(s) to exportstrings
--output-path(Required) Output path (file path or stdout (-))string
--startStart time to export (RFC3339 format)string

Examples

Export all data in a bucket as line protocol
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --output-path path/to/export.lp
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --output-path -
Export data in measurements as line protocol
# Export a single measurement
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --measurement example-measurement \
  --output-path path/to/export.lp

# Export multiple measurements
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --measurement example-measurement-1,example-measurement-2 \
  --output-path path/to/export.lp
# Export a single measurement
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --measurement example-measurement \
  --output-path -

# Export multiple measurements
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --measurement example-measurement-1,example-measurement-2 \
  --output-path -
Export data in specified time range as line protocol
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --start 2021-01-01T00:00:00Z \
  --end 2021-01-31T23:59:59Z \
  --output-path path/to/export.lp
influxd inspect export-lp \
  --bucket-id 12ab34cd56ef \
  --engine-path ~/.influxdbv2/engine \
  --start 2021-01-01T00:00:00Z \
  --end 2021-01-31T23:59:59Z \
  --output-path -

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