-
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
feat(agent): Add option to skip re-running processors after aggregators #14882
Conversation
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
Awesome @powersj! Can you please also check that invalid config options of processors are handled correctly, i.e. they produce an error!? I remember that there is some special handling for those as they are parsed twice...
Do you off-hand recall what might have existing tests for parsing twice (e.g. agent? config? procesosrs themselves)? |
Looked it up and it seems this is covered by the tests. Sorry for the noise! |
Summary
By default, after an aggregator is run the processors are run again. This can be helpful for users of aggregators to apply similar rules, however, this can also be very, very unexpected. As this behavior can result in aggregated values from getting scaled or computed against a second time.
While users can use the metric selectors to possibly omit the second run, it is nice to have a flag to remove this behavior entirely when it is not needed.
This introduces the
skip_processors_after_aggregators
config option, false by default.Using a config with a processor that multiplies a float field by 10 each time it is run, by default:
When set to true, note how the value is no longer scaled again.
Checklist
Related issues
fixes: #7993