Telegraf Controller 1.1 adds fleet-wide configuration management features: global constants for defining shared values once, configuration groups for bundling configs as role profiles, and configuration aliases for human-readable identifiers instead of UUIDs. Configuration versioning tracks every change with a diff-and-revert audit trail, while high availability (Telegraf Enterprise only) lets multiple Controller instances share a database with automatic failover so agents keep pulling configs if an instance goes down. Together these features let a single edit—like changing an output endpoint—propagate across an entire fleet on the next config pull.
Table of contents
High availability (Telegraf Enterprise)Configuration versioningGlobal constantsConfiguration groupsConfiguration aliasesOne change, fleet-wideWhat’s free and what requires Telegraf EnterpriseGet startedFAQQuestions this post answers
What new features does Telegraf Controller 1.1 add for managing agent fleets?
Telegraf Controller 1.1 adds high availability, configuration versioning, global constants, configuration groups, and configuration aliases. Global constants let a shared value like an output endpoint be defined once and referenced with ::{constant_name} syntax. Configuration groups bundle multiple configs into an ordered unit agents retrieve in one request, and aliases give configs human-readable names instead of UUIDs. Track new observability tooling releases like Telegraf Controller updates on daily.dev.
Is high availability for Telegraf Controller free or does it require Telegraf Enterprise?
High availability for Telegraf Controller requires Telegraf Enterprise; it is not included in the free version. It runs multiple Controller instances from a shared database with automatic failover, so agents keep pulling configuration and reporting health if one instance goes down. Configuration versioning, aliases, global constants, and configuration groups are all available free. Compare free versus paid tiers of infrastructure tools like Telegraf Controller on daily.dev.
How do Telegraf Controller configuration groups work as role profiles for different server types?
Configuration groups bundle multiple configs into an ordered unit that agents retrieve in a single request, composing by reference rather than by copy. A base config with system inputs every host runs can be combined with role-specific configs for a web server or database host, so tuning the base config once updates every role without maintaining drifting copies. Developers building fleet-wide config strategies can find patterns like this on daily.dev.