Documentation

telegraf config migrate

The telegraf config migrate command reads the configuration files specified in the --config or --config-directory and attempts to migrate plugins or options that are currently deprecated to the recommended replacements. If no configuration file is explicitly specified, the command reads the default locations and uses those configuration files.

Migrated files are stored with a .migrated suffix at the location of the source configuration files. If migrating remote configurations, the migrated configuration is stored in the current directory using the URL as the filename with a .migrated suffix.

Test migrated configuration files

We strongly recommend testing migrated configuration files before using them in production.

Usage

telegraf [global-flags] config migrate [flags]

Flags

FlagDescription
--forceForces overwriting of an existing migration file
-h--helpShow command help

Examples

Migrate a single configuration file

To migrate the file mysettings.conf, run the following command:

telegraf --config mysettings.conf config migrate

Migrate a configuration directory

To migrate all configurations files in the ~/telegraf/conf/ directory, use the following command:

telegraf --config-directory ~/telegraf/conf/ config migrate

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.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: