-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Rename metrics to follow the naming convention #8401
Rename metrics to follow the naming convention #8401
Conversation
Signed-off-by: João Vilaça <jvilaca@redhat.com>
/retest |
/cc @enp0s3 |
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.
/approve
NOTE: for the long-term, an automatic validation should take place for such occasions.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enp0s3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@machadovilaca: The following test failed, say
Instructions 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/test-infra repository. I understand the commands that are listed here. |
/cherry-pick release-0.53 |
@machadovilaca: #8401 failed to apply on top of branch "release-0.53":
In response to this:
Instructions 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/test-infra repository. |
Signed-off-by: João Vilaça jvilaca@redhat.com
What this PR does / why we need it:
kubevirt_vmi_memory_domain_total_bytes
andkubevirt_vmi_filesystem_total_bytes
were not following the metrics naming convention that we are following in the other metrics. This PR renames them.kubevirt_vmi_memory_domain_total_bytes
->kubevirt_vmi_filesystem_capacity_bytes_total
kubevirt_vmi_filesystem_total_bytes
->kubevirt_vmi_memory_domain_bytes_total
Release note: