We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
diskUtilization := float64(diskUsed) / float64(diskFree) * 100
when it should be calculated like
diskUtilization := float64(diskUsed) / float64(diskFree+diskUsed) * 100
Steps to reproduce Looking at a live environment in Google Cloud noticed the value was incorrect.
What did you expect to see?
For our example storage uncommitted was 10539597824 bytes and committed was 139787059517 bytes which should be calculated as
What did you see instead?
The value was rather 139787059517 bytes ÷ (10539597824 bytes) * 100% = 1398 %
Additional context
Will have a PR shortly to fix calculation.
The text was updated successfully, but these errors were encountered:
@schmikei, please create separate issues for the various changes you are proposing.
Sorry, something went wrong.
There appear to be three unrelated changes here, so an issue for the cpu metric, and another for the resource label.
Alright I'll separate them out 👍
vcenter.cluster.name
vcenter.datastore
@djaglowski I think this should work but let me know if anything needs changes!
vcenter.vm.cpu.utilization
Successfully merging a pull request may close this issue.
Describe the bug
when it should be calculated like
Steps to reproduce
Looking at a live environment in Google Cloud noticed the value was incorrect.
What did you expect to see?
For our example storage uncommitted was 10539597824 bytes and committed was 139787059517 bytes which should be calculated as
What did you see instead?
The value was rather
139787059517 bytes ÷ (10539597824 bytes) * 100% = 1398 %
Additional context
Will have a PR shortly to fix calculation.
The text was updated successfully, but these errors were encountered: