influx export command exports existing resources as an InfluxDB template.
For detailed examples of exporting InfluxDB templates, see
Create an InfluxDB template.
influx export [flags] influx export [command]
|all||Export all resources in an organization as a template|
|stack||Export all resources associated with a stack as a template|
|Flag||Description||Input Type||Maps to ?|
|Comma-separated list of bucket IDs||string|
|Comma-separated list of check IDs||string|
|Comma-separated list of dashboard IDs||string|
|Comma-separated list of notification endpoint IDs||string|
|Template output file. Defaults to stdout. Use ||string|
|Help for the |
|HTTP address of InfluxDB (default ||string|
|Comma-separated list of label IDs||string|
|Resource type associated with all IDs via stdin||string|
|Comma-separated list of notification rule IDs||string|
|Skip TLS certificate verification|
|Stack ID to include resources from in export||string|
|Comma-separated list of task IDs||string|
|Comma-separated list of Telegraf configuration IDs||string|
|Comma-separated list of variable IDs||string|
# Export buckets by ID influx export --buckets=$ID1,$ID2,$ID3 # Export buckets, labels, and dashboards by ID influx export \ --buckets=$BID1,$BID2,$BID3 \ --labels=$LID1,$LID2,$LID3 \ --dashboards=$DID1,$DID2,$DID3 # Export all resources associated with a stack influx export --stack-id $STACK_ID # Export resources associated with a stack and resources # *not* associated with the stack influx export --stack-id $STACK_ID --buckets $BUCKET_ID
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support or submit feedback, the following resources are available:
- Post in the InfluxData Community.
- Submit documentation issues to the InfluxDB 2.0 documentation repository.
- Submit InfluxDB issues to the InfluxDB repository.
For our InfluxDB Cloud customers, InfluxData Support is also available.