You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2021. It is now read-only.
Between subsequent scrapes, values of this metric are not often increasing (at least for some VMs). For example, I have a VM where over 3 hours the counter value only changed 3 times!!
I notice the same thing when I run virst dominfo. CPU time doesn't change very often.
However, if I use virsh domstats, cpu.time increases every time.
Would it be possible to use the stats API instead of the info API
Thanks
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Between subsequent scrapes, values of this metric are not often increasing (at least for some VMs). For example, I have a VM where over 3 hours the counter value only changed 3 times!!
I notice the same thing when I run
virst dominfo
.CPU time
doesn't change very often.However, if I use
virsh domstats
,cpu.time
increases every time.Would it be possible to use the stats API instead of the info API
Thanks
The text was updated successfully, but these errors were encountered: