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

Inherit previous instance's stats in statsd plugin. #887

Closed

Conversation

entertainyou
Copy link
Contributor

This way, after a reload, the stats wont restart again at least for the
counter type.

This way, after a reload, the stats wont restart again at least for the
counter type.
@entertainyou
Copy link
Contributor Author

I dont know if this is the right way to fix it, but it works, :)

@sparrc
Copy link
Contributor

sparrc commented Mar 18, 2016

cool! makes sense for this plugin :)

@sparrc sparrc closed this in 18f4afb Mar 18, 2016
sparrc added a commit that referenced this pull request Dec 20, 2016
this basically reverts #887

at some point we might want to do some special handling of reloading
plugins and keeping their state intact, but that will need to be done at
a higher level, and in a way that is thread-safe for multiple input
plugins of the same type.

Unfortunately this is a rather large feature that will not have a quick
fix available for it.

fixes #1975
fixes #2102
njwhite pushed a commit to njwhite/telegraf that referenced this pull request Jan 31, 2017
this basically reverts influxdata#887

at some point we might want to do some special handling of reloading
plugins and keeping their state intact, but that will need to be done at
a higher level, and in a way that is thread-safe for multiple input
plugins of the same type.

Unfortunately this is a rather large feature that will not have a quick
fix available for it.

fixes influxdata#1975
fixes influxdata#2102
maxunt pushed a commit that referenced this pull request Jun 26, 2018
this basically reverts #887

at some point we might want to do some special handling of reloading
plugins and keeping their state intact, but that will need to be done at
a higher level, and in a way that is thread-safe for multiple input
plugins of the same type.

Unfortunately this is a rather large feature that will not have a quick
fix available for it.

fixes #1975
fixes #2102
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants