Dual write to InfluxDB OSS and InfluxDB Cloud

If you want to back up your data in two places, or if you’re migrating from InfluxDB OSS to InfluxDB Cloud Dedicated, you may want to set up Telegraf to dual write.

Use Telegraf to write to both InfluxDB OSS and InfluxDB Cloud Dedicated simultaneously.

The sample configuration below uses:

Use the configuration below to write your data to both OSS and Cloud Dedicated instances simultaneously.

Sample configuration

# Include any other input, processor, or aggregator plugins that you want to include in your configuration.

# Send data to InfluxDB OSS v2
  ## The URLs of the InfluxDB instance.
  ## Multiple URLs can be specified for a single cluster, only ONE of the
  ## urls will be written to each interval.
  ## urls exp:
  urls = ["http://localhost:8086"]

  ## OSS token for authentication.
  token = "${INFLUX_TOKEN_OSS}"

  ## Organization is the name of the organization you want to write to. It must already exist.
  organization = "ORG_NAME_OSS"

  ## Destination bucket to write to.
  bucket = "BUCKET_NAME_OSS"

# Send data to InfluxDB Dedicated instance
  ## The URLs of the InfluxDB Cloud instance.

  urls = [""]

  ## Cloud token for authentication.
  token = "${INFLUX_TOKEN}"

  ## For InfluxDB Cloud Dedicated, set organization to an empty string.
  organization = ""

  ## Destination bucket to write into.
  bucket = "DATABASE_NAME"

Was this page helpful?

Thank you for your feedback!

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: