Documentation

telegraf config create

The telegraf config create command returns a full Telegraf configuration containing all plugins as an example. You can also apply section or plugin filters to reduce the output to the plugins you need.

Usage

telegraf [global-flags] config create [flags]

Flags

FlagDescription
--section-filterFilter sections to print separated by : (Valid values are agent, global_tags, outputs, processors, aggregators and inputs)
--input-filterFilter inputs to enable separated by :
--output-filterFilter outputs to enable separated by :
--aggregator-filterFilter aggregators to enable separated by :
--processor-filterFilter processors to enable separated by :
--secretstore-filterFilter secret-stores to enable separated by :
-h--helpShow command help

Examples

Create a full configuration

telegraf config create

Create a full configuration as save it to a file

telegraf config create > telegraf.conf

Create a configuration with specific sections and plugins

To print a configuration containing only a Modbus input plugin and an InfluxDB v2 output plugin, run the following:

telegraf config create \
  --section-filter "inputs:outputs" \
  --input-filter "modbus" \
  --output-filter "influxdb_v2"

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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