-
Notifications
You must be signed in to change notification settings - Fork 1k
Add EstimateComponentsPlugins support to estimator framework
#6864
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
Hi @RainbowMango ,
In order to differentiate the metrics between
EstimateReplicaandEstimateComponentsplugins, I decided to introduce a new metrics withEstimateComponentslabel and plan to useEstimateReplicato replace the oldEstimatorlabel.Additionally, to avoid breaking change I decided to emit the same metrics twice but with different label.
What do you think? I am OK with reusing
EstimatorbutEstimateReplicamight be clearer.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'm okay with introducing
EstimateReplicato replaceEstimator. However, if we proceed with this change, the release note should include an additional section on the deprecation of the existing metrics.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'm OK with this way by introducing a new metric to deprecate the old one.
+1 on the release note
In addition, I realized both the old and new label names are written in camel case, which is not recommended.
I failed to find some documentation about the naming rule, but there is a metrics linter in the Prometheus project:
https://github.com/RainbowMango/client_golang/blob/e729ba11961abb3a50910c324221d06a35bdce4f/prometheus/testutil/promlint/validations/generic_name_validations.go#L74-L89
PS: I introduced this tool to Kubernetes several years ago, but I didn't get a chance to do the same thing in Karmada. I think Karmada should adopt this tool as well.
Uh oh!
There was an error while loading. Please reload this page.
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 the info! Updated the label values with snake case and the release note.
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.
Hey, I need to correct my previous comment about the label format, according to the validation tools I linked above, only the label
nameshould be written insnake_case. Actually, what we are talking about here is thevalue, I don't see any rules for it.I see you updated the label value to
snake_case, which also looks fine to me.