Feature Request
Proposal:
Reload configuration via URL
Current behavior:
The only time the Telegraf config is (re)loaded is at agent startup. Agent currently does not poll for new configuration via URL-based config.
Desired behavior:
Reload configuration based on a designated frequency for the reload and include a jitter time to ensure we avoid a thundering herd for the reading of the config from the server hosting it.
Use case:
As it stands, the agent requests its configuration at startup based on the supplied URL, but users can modify the configuration at any point afterwards. Such a configuration change requires a signaling mechanism to trigger Telegraf to reload the config -- which doesn't currently exist. A simple time-based mechanism can ensure that all active agents will refresh within some reasonable time window.
One workaround is that in Linux, you can use the Exec plugin to run a “HUP” against the agent every hour, which triggers Telegraf to reload. But there is no equivalent HUP for Windows, and so whilst killing the agent and while waiting for Windows ServiceControlManager to restart it, there is a short blackout period (as well as an error in the Windows Event Log). These are not ideal.
Feature Request
Proposal:
Reload configuration via URL
Current behavior:
The only time the Telegraf config is (re)loaded is at agent startup. Agent currently does not poll for new configuration via URL-based config.
Desired behavior:
Reload configuration based on a designated frequency for the reload and include a
jittertime to ensure we avoid a thundering herd for the reading of the config from the server hosting it.Use case:
As it stands, the agent requests its configuration at startup based on the supplied URL, but users can modify the configuration at any point afterwards. Such a configuration change requires a signaling mechanism to trigger Telegraf to reload the config -- which doesn't currently exist. A simple time-based mechanism can ensure that all active agents will refresh within some reasonable time window.
One workaround is that in Linux, you can use the Exec plugin to run a “HUP” against the agent every hour, which triggers Telegraf to reload. But there is no equivalent HUP for Windows, and so whilst killing the agent and while waiting for Windows ServiceControlManager to restart it, there is a short blackout period (as well as an error in the Windows Event Log). These are not ideal.