metrics/features: Fix counter metrics to use Set() instead of Add() #41382
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace Add(1) with Set(1) for all feature metrics in both daemon and operator components. These metrics represent boolean feature states that should be set to 1 when enabled, not incremented. Using Add(1) causes metrics to accumulate over time and produce incorrect values when the metrics are updated multiple times, leading to misleading monitoring data. Signed-off-by: André Martins <andre@cilium.io>
|
/test |
joestringer
approved these changes
Aug 26, 2025
18 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace Add(1) with Set(1) for all feature metrics in both daemon and operator components. These metrics represent boolean feature states that should be set to 1 when enabled, not incremented. Using Add(1) causes metrics to accumulate over time and produce incorrect values when the metrics are updated multiple times, leading to misleading monitoring data.