Documentation

Use the Telegraf Builder

Telegraf Controller is in Private Alpha

Telegraf Controller is in private alpha. If you are interested in being a part of the private alpha program, please sign up:

Sign Up for the Alpha

While in alpha, Telegraf Controller is not meant for production use. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please submit an issue. We welcome any and all contributions.

The Telegraf Builder is a visual interface for managing and configuring Telegraf plugins in a configuration. The builder is available when creating or updating a configuration.

Telegraf Builder in Telegraf Controller

The Telegraf builder is divided into two main panes:

Plugin Library pane

The Plugin Library pane provides a list of all Telegraf plugins supported in the builder grouped by plugin type.

The Telegraf Builder does not support all Telegraf plugins

We are in the process of adding support for more Telegraf plugins in the Telegraf Builder. You can use plugins that are not currently supported by the builder, but you must add and edit them with the Code Editor.

  • Search plugins: Use the search bar in the Plugin Library pane to search for Telegraf plugins. Search by plugin name, identifier, or description.
  • Add plugins to your configuration: Click next to the plugin to add it to your configuration.

Configuration pane

The Configuration pane lets you manage agent and plugin-specific settings. Configuration options and plugins are each represented by “cards”. Click on a card or expand or hide its contents.

Each configuration has at least two cards: Agent Settings and Global Tags.

Agent settings

Agent settings are those that specify how the agent runs rather than plugin-specific settings. Agent settings only need to be included in a configuration when they vary from the default Telegraf agent settings.

To include agent settings in your configuration:

  1. On the Agent Settings card, enable the Include in config toggle.
  2. Define custom settings for any of the available Telegraf agent settings.

Global tags

Telegraf applies global tags to all metrics that it emits. Global tags are not required and only need to be included in a configuration when set.

To include global tags in your configuration:

  1. On the Global Tags card, enable the Include in config toggle.
  2. Click Add Global Tag.
  3. Provide a key and a value for the global tag.
  4. Repeat steps 2-3 for additional global tags.

Plugin cards

The Telegraf Builder represents each Telegraf plugin as a card. Plugin cards have three tabs:

Plugin

The Plugin tab in a plugin card lets you customize settings specific to that plugin.

You can use dynamic values when defining plugin settings in the Telegraf Builder.

Customize

The Customize tab in a plugin card lets you apply plugin customizations including the following:

  • Add a plugin alias: Aliases help to identify plugins in your configuration. They are especially helpful when you have more than one of the same plugin. When you define a plugin alias, the builder uses the alias as the plugin name on the plugin card.

  • Add configuration labels: Telegraf configuration labels let you label and select what plugins to run when starting Telegraf. For more information about using labels and selectors, see Plugin selection via labels and selectors

  • Other customizations specific to the plugin type

Filter

The Filter tab on a plugin card lets you add metric filters to the plugin. These filters include namepass, namedrop, tagpass, tagdrop, and others.

For more information about using Telegraf plugin filters, see Metric filtering.

Remove a plugin from the configuration

To remove a plugin from the configuration, click the icon on the plugin card.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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