Documentation

influxd inspect export-lp

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

Flag Description Input type
--bucket-id (Required) Bucket ID string
--compress Compress output with gzip
--end End time to export (RFC3339 format) string
--engine-path (Required) Path to persistent InfluxDB engine files string
-h --help Help for the export-lp command.
--log-level Log-level (debug, info (default), or error) string
--measurement Measurement name(s) to export strings
--output-path (Required) Output path (file path or stdout (-)) string
--start Start 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!


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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.