Automatically configure Telegraf

The InfluxDB user interface (UI) can automatically create Telegraf configuration files based on user-selected Telegraf plugins. This article describes how to create a Telegraf configuration in the InfluxDB UI and start Telegraf using the generated configuration file.

View the requirements for using Telegraf with InfluxDB 2.7.

Create a Telegraf configuration

  1. Open the InfluxDB UI (default: localhost:8086).

  2. In the navigation menu on the left, select Data (Load Data) > Telegraf.

  3. Click Create Configuration.

  4. In the Bucket dropdown, select the bucket where Telegraf will store collected data.

  5. Select one or more of the available plugin groups and click Continue.

  6. Review the list of Plugins to Configure for configuration requirements. Plugins listed with a require no additional configuration. To configure a plugin or access plugin documentation, click the plugin name.

  7. Provide a Telegraf Configuration Name and an optional Telegraf Configuration Description.

  8. Adjust configuration settings as needed. To find configuration settings for a specific plugin, see Telegraf plugins.

  9. Click Save and Test.

  10. The Test Your Configuration page provides instructions for how to start Telegraf using the generated configuration. See Start Telegraf below for detailed information about what each step does.

  11. Once Telegraf is running, click Listen for Data to confirm Telegraf is successfully sending data to InfluxDB. Once confirmed, a Connection Found! message appears.

  12. Click Finish. Your Telegraf configuration name and the associated bucket name appears in the list of Telegraf configurations.


If you plan to monitor a Windows host using the System plugin, you must complete the following steps.

  1. In the list of Telegraf configurations, double-click your Telegraf configuration, and then click Download Config.

  2. Open the downloaded Telegraf configuration file and replace the [[inputs.processes]] plugin with one of the following Windows plugins, depending on your Windows configuration:

  3. Save the file and place it in a directory that telegraf.exe can access.

Start Telegraf

Requests to the InfluxDB v2 API must include an API token. A token identifies specific permissions to the InfluxDB instance.

Configure your token as an environment variable

  1. Find your API token. For information about viewing tokens, see View tokens.

  2. To configure your API token as the INFLUX_TOKEN environment variable, run the command appropriate for your operating system and command-line tool:

export INFLUX_TOKEN=YourAuthenticationToken
$env:INFLUX_TOKEN = "YourAuthenticationToken"
set INFLUX_TOKEN=YourAuthenticationToken
# Make sure to include a space character at the end of this command.

Start the Telegraf service

Start the Telegraf service using the -config flag to specify the location of the generated Telegraf configuration file.

  • For Windows, the location is always a local file path.
  • For Linux and macOS, the location can be a local file path or URL.

Telegraf starts using the Telegraf configuration pulled from InfluxDB API.

InfluxDB host URLs and ports differ between InfluxDB OSS and InfluxDB Cloud. For the exact command, see the Telegraf configuration Setup Instructions in the InfluxDB UI.

telegraf -config http://localhost:8086/api/v2/telegrafs/0xoX00oOx0xoX00o

Manage Telegraf configurations

For more information about managing Telegraf configurations in InfluxDB, see Telegraf configurations.

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: