-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
fix(processors): Correctly setup processors #12081
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for jumping on this one!
Sorry, meant to leave a comment @srebhan need to resolve a quick conflict |
ec72d4c
to
7dfd145
Compare
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 👍 This pull request doesn't change the Telegraf binary size 📦 Click here to get additional PR build artifactsArtifact URLs |
(cherry picked from commit 87125f0)
resolves #12080
resolves influxdata/influxdata-docker#647
This PR fixes a processor conversion fallout leading to potentially missing metrics when using processors in combination with aggregators, here especially the
dedup
processor. The background is that PR #11600 changed the way processors are initialized. Before the mentioned PR new and independent instances of a processors were created to be run before and after an aggregator. #11600 then changes this to only create a single instance, shared between the processing steps (before and after the aggregator) leading to side-effects. This is especially noticeable in thededup
processor as in the second processing step (after aggregation) the same instance sees the same metric twice and removes it while no metrics was emitted to the output in the first processing step (before the aggregator), leading to completely dropping all metrics.This PR now creates to independent instances of the processor for the two processing steps just as before #11600.