Bug 2223654 - VMI CPU metrics are counters not gauges
Summary: VMI CPU metrics are counters not gauges
Keywords:
Status: POST
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Metrics
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.14.0
Assignee: João Vilaça
QA Contact: Ahmad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 12:51 UTC by Shirly Radco
Modified: 2023-08-11 13:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 10138 0 None Merged Change kubevirt_vmi_*_usage_seconds from Gauges to Counters 2023-08-09 11:08:12 UTC
Github kubevirt kubevirt pull 10273 0 None open [release-1.0] Change kubevirt_vmi_*_usage_seconds from Gauges to Counters 2023-08-11 13:26:40 UTC
Github kubevirt kubevirt pull 10276 0 None open [release-0.59] Change kubevirt_vmi_*_usage_seconds from Gauges to Counters 2023-08-11 13:26:40 UTC
Red Hat Issue Tracker CNV-31131 0 None None None 2023-07-18 12:53:02 UTC

Description Shirly Radco 2023-07-18 12:51:18 UTC 
Description of problem:
The metrics added in  https://github.com/kubevirt/kubevirt/pull/8774
- kubevirt_vmi_cpu_system_seconds
- kubevirt_vmi_cpu_user_seconds
- kubevirt_vmi_cpu_usage_seconds

are counters.
We need to update them and the documentation for them accordingly.

Version-Release number of selected component (if applicable):
4.13.0

How reproducible:
100%

Steps to Reproduce:
1. Create a VM.
2. Run load on the VM CPU
3. Check the CPU metric value

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.