Use Telegraf to dual write to InfluxDB

Use Telegraf to write your data simultaneously to multiple InfluxDB instances or clusters. This method, known as “dual writing,” is useful for backing up data to a separate instance or for migrating from other versions of InfluxDB to InfluxDB 3 Core.

The following example configures Telegraf for dual writing to InfluxDB 3 Core and an InfluxDB v2 OSS instance.

• The InfluxDB v2 output plugin twice–the first pointing to InfluxDB 3 Core and the other to an InfluxDB v2 OSS instance.

• Two different tokens–one for InfluxDB v2 OSS and one for InfluxDB 3 Core. Configure both tokens as environment variables and use string interpolation in your Telegraf configuration file to reference each environment variable.

  While in beta, InfluxDB 3 Core does not require an authorization token. For the token option, provide an arbitrary, non-empty token string.

Sample configuration

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

# Send data to InfluxDB 3 Core
[[outputs.influxdb_v2]]
  ## The InfluxDB 3 Core URL
  urls = ["http://localhost:8181"]
  ## InfluxDB 3 Core authorization token
  token = "${INFLUX_TOKEN}"
  ## For InfluxDB 3 Core, set organization to an empty string
  organization = ""
  ## Destination database to write into
  bucket = "DATABASE_NAME"

# Send data to InfluxDB v2 OSS
[[outputs.influxdb_v2]]
  ## The InfluxDB v2 OSS URL
  urls = ["http://localhost:8086"]
  ## OSS token for authentication
  token = "${INFLUX_TOKEN_OSS}"
  ## Organization is the name of the organization you want to write to.
  organization = "ORG_NAME_OSS"
  ## Destination bucket to write to
  bucket = "BUCKET_NAME_OSS"

Telegraf lets you dual write data to any version of InfluxDB using the influxdb (InfluxDB v1) and influxdb_v2 output plugins. A single Telegraf agent sends identical data sets to all target outputs. You cannot filter data based on the output.