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
When using the vpsheredb checks, it is currently the case that overclocked CPU values are not displayed cleanly, which is unfortunately due to the fact that these values cannot be obtained from the VMWare API.
Currently it looks like this: [CRITICAL] 13.5 GHz out of 12 GHz used, -1.53E+3 GHz (-12.75%) free
The exponential representation should be avoided.
To better recognize that a CPU is overclocked, it would also be useful to have a percentage display of the utilization: [CRITICAL] 13.5 GHz (112.75%) out of 12 GHz used, -1.53 GHz (-12.75%) free
When using the vpsheredb checks, it is currently the case that overclocked CPU values are not displayed cleanly, which is unfortunately due to the fact that these values cannot be obtained from the VMWare API.
Currently it looks like this:
[CRITICAL] 13.5 GHz out of 12 GHz used, -1.53E+3 GHz (-12.75%) free
The exponential representation should be avoided.
To better recognize that a CPU is overclocked, it would also be useful to have a percentage display of the utilization:
[CRITICAL] 13.5 GHz (112.75%) out of 12 GHz used, -1.53 GHz (-12.75%) free
Your Environment
The text was updated successfully, but these errors were encountered: