Documentation

influx export all

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 3 storage engine.

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

To export resources as a template, you must use the Operator token created for the initial InfluxDB user or an All Access token. For information about creating an All Access API token, see Create an API token.

Usage

influx export all [flags]

Flags

FlagDescriptionInput TypeMaps to ?
-c--active-configCLI configuration to use for commandstring
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-f--fileTemplate output file. Defaults to stdout. Use .yml or .json file extensions.string
--filterSpecify resources to export by labelName or resourceKind (format: --filter=labelName=example)stringArray
-h--helpHelp for the export all command
--hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
--http-debugInspect communication with InfluxDB servers.string
-o--orgOrganization name that owns the resources (mutually exclusive with --org-id)stringINFLUX_ORG
--org-idOrganization ID that owns the resources (mutually exclusive with --org)stringINFLUX_ORG_ID
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstringINFLUX_TOKEN

Resources

The following resources can be exported:

  • Bucket
  • Check
  • CheckDeadman
  • CheckThreshold
  • Dashboard
  • Label
  • NotificationEndpoint
  • NotificationEndpointHTTP
  • NotificationEndpointPagerDuty
  • NotificationEndpointSlack
  • NotificationRule
  • Task
  • Telegraf
  • Variable

For additional information on each resource, please see template resources.

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 all resources in an organization as a template
influx export all
Export all bucket resources as a template
influx export all --filter=resourceKind=Bucket
Export all resources associated with label Foo
influx export all --filter=labelName=Foo
Export all bucket resources and with label Foo
influx export all \
	--filter=resourceKind=Bucket \
	--filter=labelName=Foo
Export all bucket or dashboard resources with label Foo
influx export all \
	--filter=resourceKind=Bucket \
	--filter=resourceKind=Dashboard \
	--filter=labelName=Foo

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

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

InfluxDB Cloud Serverless