Documentation

influx export

Not supported in InfluxDB Cloud Serverless

While this command is included in the influx CLI , this functionality is not available in InfluxDB Cloud Serverless organizations powered by the InfluxDB v3 storage engine.

The influx export command exports existing resources as an InfluxDB template. For detailed examples of exporting InfluxDB templates, see Create an InfluxDB template.

Usage

influx export [flags]
influx export [command]

Available subcommands

SubcommandDescription
allExport all resources in an organization as a template
stackExport all resources associated with a stack as a template

Flags

FlagDescriptionInput TypeMaps to ?
-c--active-configCLI configuration to use for commandstring
--bucket-namesComma-separated list of bucket namesstring
--bucketsComma-separated list of bucket IDsstring
--check-namesComma-separated list of check namesstring
--checksComma-separated list of check IDsstring
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
--dashboard-namesComma-separated list of dashboard namesstring
--dashboardsComma-separated list of dashboard IDsstring
--endpoint-namesComma-separated list of notification endpoint namesstring
--endpointsComma-separated list of notification endpoint IDsstring
-f--fileTemplate output file. Defaults to stdout. Use .yml or .json file extensions.string
-h--helpHelp for the export command
--hostHTTP address of InfluxDB (default http://localhost:9999)stringINFLUX_HOST
--http-debugInspect communication with InfluxDB servers.string
--label-namesComma-separated list of label namesstring
--labelsComma-separated list of label IDsstring
--resource-typeResource type associated with all IDs via stdinstring
--rule-namesComma-separated list of notification rule namesstring
--rulesComma-separated list of notification rule IDsstring
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
--stack-idStack ID to include resources from in exportstring
--task-namesComma-separated list of task namesstring
--tasksComma-separated list of task IDsstring
--telegraf-config-namesComma-separated list of Telegraf configuration namesstring
--telegraf-configsComma-separated list of Telegraf configuration IDsstring
-t--tokenAPI tokenstringINFLUX_TOKEN
--variable-namesComma-separated list of variable namesstring
--variablesComma-separated list of variable IDsstring

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Export buckets by ID
influx export --buckets 0Xx0oox00XXoxxoo1,0Xx0oox00XXoxxoo2
Export buckets, labels, and dashboards by ID
influx export \
  --buckets 0Xx0oox00XXoxxoo1,0Xx0oox00XXoxxoo2 \
  --labels o0x0oox0Xxoxx001,o0x0oox0Xxoxx002 \
  --dashboards 0XxXooXoo0xooXo0X1,0XxXooXoo0xooXo0X2
Export buckets, labels, and dashboards by name
influx export \
  --bucket-names bucket1,bucket2,bucket3 \
  --label-names label1,label2,label3 \
  --dashboard-names dashboard1,dashboard2,dashboard3
Export all resources associated with a stack
influx export --stack-id 0Xx0oox00XXoxxoo1
Export resources both associated and not associated with a stack
influx export \
  --stack-id 0Xx0oox00XXoxxoo1 \
  --buckets o0x0oox0Xxoxx001,0XxXooXoo0xooXo0X2 \
  --dashboard-names bucket1

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:

InfluxDB Cloud Serverless