feat: add enforcement latency metric with operation labels - #450
feat: add enforcement latency metric with operation labels#450rawadhossain wants to merge 1 commit into
Conversation
✅ Deploy Preview for node-readiness-controller canceled.
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rawadhossain The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @rawadhossain. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cc @ajaysundark |
|
/cc @AvineshTripathi |
AvineshTripathi
left a comment
There was a problem hiding this comment.
/lgtm
left some minor question
| labelNames[l.GetName()] = true | ||
| } | ||
| } | ||
| for _, want := range []string{"rule", "operation"} { |
There was a problem hiding this comment.
Do we really need this check? CollectAndCompare should already check this right?
There was a problem hiding this comment.
yeah fair, thought to have a cleaner failure message thats why put it there, but you're right its redundant. Removed it.
|
/ok-to-test |
9b1a813 to
68de79c
Compare
68de79c to
bd881be
Compare
|
@AvineshTripathi i dont know why the CI check is failing in every PR. From my end everything looks fine. |
|
It's seems slack invite redirection is down. I have raised this in their channel. Will ping you there |
AvineshTripathi
left a comment
There was a problem hiding this comment.
/lgtm
left a minor suggestion
Tested the metrics part locally. However, didn't run the scale test though
| } | ||
|
|
||
| recordLatency := func(operation string) { | ||
| recordLatency := func(operation string, enforcementOperation metrics.EnforcementOperation) { |
There was a problem hiding this comment.
why not both metrics.<metrics-name>. inconsistency here
|
@rawadhossain please resolve the conflicts too. Thanks! |
bd881be to
3ce515a
Compare
3ce515a to
b07d00d
Compare
Signed-off-by: Rawad Hossain <rawad.hossain00@gmail.com>
b07d00d to
d959fad
Compare
|
@AvineshTripathi resolved the conflicts and inconsistency. |
AvineshTripathi
left a comment
There was a problem hiding this comment.
/lgtm
wouldn't we get conflicts when one of the PR gets merged regarding the util func
|
Yes probably we would. Will have to resolve the conflict afterwards. |
Description
node_readiness_enforcement_latency_secondswithadd/removeoperation labels, keepingnode_readiness_reconciliation_latency_secondsunchanged.monitoring.mdanddocs/TEST_README.md.from the design doc:
Related to #446
Type of Change
/kind feature
Testing
make test,make lint,go vet,gofmt -lall pass.Checklist
make testpassesmake lintpasses