Documentation

Configure Telegraf to write to InfluxDB 3 Enterprise

Use the Telegraf influxdb_v2 output plugin to collect and write metrics to InfluxDB 3 Enterprise. This plugin uses the InfluxDB v2 HTTP API write endpoint available with InfluxDB 3 Enterprise. Learn how to enable and configure the influxdb_v2 output plugin to write data to InfluxDB 3 Enterprise.

View the requirements for using Telegraf with InfluxDB 3 Enterprise.

Configure Telegraf input and output plugins

Configure Telegraf input and output plugins in the Telegraf configuration file (typically named telegraf.conf). Input plugins collect metrics. Output plugins define destinations where metrics are sent.

This guide assumes you have already installed InfluxDB 3 Enterprise and have been through the getting started guide.

Add Telegraf plugins

To add any of the available Telegraf plugins, follow the steps below.

  1. Find the plugin you want to enable from the complete list of available Telegraf plugins.
  2. Click View to the right of the plugin name to open the plugin page on GitHub. For example, view the MQTT plugin GitHub page.
  3. Copy and paste the example configuration into your Telegraf configuration file (typically named telegraf.conf).

Enable and configure the InfluxDB v2 output plugin

To send data to InfluxDB 3 Enterprise, enable the influxdb_v2 output plugin in the telegraf.conf.

[[outputs.influxdb_v2]]
  urls = ["http://localhost:8181"]
  token = "
AUTH_TOKEN
"
organization = "" bucket = "
DATABASE_NAME
"

Replace the following:

  • DATABASE_NAME: the name of the database to write data to
  • AUTH_TOKEN: your InfluxDB 3 Enterprise token. Store this in a secret store or environment variable to avoid exposing the raw token string.

The InfluxDB output plugin configuration contains the following options:

urls

An array of URL strings. To write to InfluxDB 3 Enterprise, include your InfluxDB 3 Enterprise URL:

["http://localhost:8181"]

token

Your InfluxDB 3 Enterprise authorization token.

Store your authorization token as an environment variable

To prevent a plain text token in your Telegraf configuration file, we recommend that you store the token as an environment variable and then reference the environment variable in your configuration file using string interpolation. For example:

[[outputs.influxdb_v2]]
  urls = ["http://localhost:8181"]
  token = "${INFLUX_TOKEN}"
  # ...

organization

For InfluxDB 3 Enterprise, set this to an empty string ("").

bucket

The name of the InfluxDB 3 Enterprise database to write data to.

An InfluxDB v2 bucket is synonymous with an InfluxDB 3 Enterprise database.

Other Telegraf configuration options

For more plugin configuration options, see the influxdb_v2 output plugin README on GitHub.

Start Telegraf

Start the Telegraf service using the --config flag to specify the location of your telegraf.conf.

telegraf --config /path/to/custom/telegraf.conf

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.

Read more

New in InfluxDB 3.4

Key enhancements in InfluxDB 3.4 and the InfluxDB 3 Explorer 1.2.

See the Blog Post

InfluxDB 3.4 is now available for both Core and Enterprise, which introduces offline token generation for use in automated deployments and configurable license type selection that lets you bypass the interactive license prompt. InfluxDB 3 Explorer 1.2 is also available, which includes InfluxDB cache management and other new features.

For more information, check out: