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.

Sign up for GitHub

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

Jump to bottom

Configuration updates / changes should trigger a reload #4

Closed
yankcrime opened this issue Mar 10, 2016 · 0 comments
Closed

Configuration updates / changes should trigger a reload #4

yankcrime opened this issue Mar 10, 2016 · 0 comments

Comments

@yankcrime
Copy link
Member

Currently, any configuration changes after the service has started fail to trigger any kind of reload so that the agent picks up the new values. This should be fixed so that they do - apparently this can be done gracefully (i.e without downtime) by sending a SIGHUP to the process - influxdata/telegraf#69
yankcrime added a commit that referenced this issue Mar 10, 2016
@yankcrime
SIGHUP the telegraf process on configuration change
ce70922 
This commit ensures that any configuration changes made after Telegraf
has been started are picked up by the agent.

Fixes #4.
@yankcrime yankcrime mentioned this issue Mar 10, 2016
Merged
stuartbfox referenced this issue in stuartbfox/puppet-telegraf Mar 31, 2016
@stuartbfox
SIGHUP the telegraf process on configuration change
db5e9ab 
This commit ensures that any configuration changes made after Telegraf
has been started are picked up by the agent.

Fixes #4.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yankcrime