Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The telegraf.conf file takes effect automatically after modification #11127

Closed
stone-98 opened this issue May 18, 2022 · 1 comment
Closed

The telegraf.conf file takes effect automatically after modification #11127

stone-98 opened this issue May 18, 2022 · 1 comment
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@stone-98
Copy link

Feature Request

The telegraf.conf file takes effect automatically after modification,and an HTTP interface is provided to modify the telegraf.conf file

Proposal:

The telegraf.conf file takes effect automatically after modification, and provides an interface for modifying the telegraf.conf file.

Current behavior:

Telegraf After modifying the telegraf.conf file, you must restart Telegraf for the new configuration to take effect.

Desired behavior:

Telegraf After modifying telegraf.conf, you do not need to restart Telegraf for the new configuration to take effect.

Use case:

The telegraf.conf file needs to be adjusted dynamically during Telegraf running.

@stone-98 stone-98 added the feature request Requests for new plugin and for new features to existing plugins label May 18, 2022
@reimda
Copy link
Contributor

reimda commented May 19, 2022

Closing as a duplicate of #7519. This functionality is not availble yet, but many users are able to work around by using the watch-config command line option (added in #9485)

@reimda reimda closed this as completed May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

No branches or pull requests

2 participants