-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[processor / spanmetricsprocessor] dropping the condition to replace _ with key_ as __ is reserved and _ is not #8057
[processor / spanmetricsprocessor] dropping the condition to replace _ with key_ as __ is reserved and _ is not #8057
Conversation
featureGate changes for sanitizing labels that start with `_`
@codeboten @Aneurysm9, since you reviewed the other related PRs, could you have a look at this one? |
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.
I will defer to @codeboten and @Aneurysm9 opinions, but I think adding Prometheus-specific logic to a component that is, in principle, independent of Prometheus, is an anti-pattern that should be avoided
updated the feature gate identifier
…ishna397/opentelemetry-collector-contrib into spanmetricsprocessor_issue
changelog update
@Aneurysm9 , @mx-psi could you please review and let me know if there're any changes pending. |
dropped processor helper import in factory.go
Description: when sanitizeLabel feature flag is enabled, labels that start with _ are not updated. labels that start with __ are sanitized irrespective of this flag since __ is reserved in prometheus and _ is not.
followed the same approach as #7112 & #7506
Link to tracking Issue:
Testing: emit a metric that has a label starting with _ and it should not be prefixed with key when skipSanitizeLabel is enabled.
Documentation: