Skip to content
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

[receiver/vcenter] Fix incorrect KBy and MBy units #14108

Merged
merged 2 commits into from
Sep 13, 2022

Conversation

BinaryFissionGames
Copy link
Contributor

@BinaryFissionGames BinaryFissionGames commented Sep 13, 2022

Description:
The vcenter receiver indicates that it uses kilobytes (kBy), but instead the units are actually kibibytes (KiBy). The vSphere API docs claims they are in kilobytes, but documentation on the data counters units indicates that they use kilobytes to mean 1024 bytes, which in UCUM is actually kibibytes (KiBy).

Similar logic applies to the MBy units. VMware, in general, seems to prefer returning in power of 2 units instead of power of 10 units.

Link to tracking Issue: Part of #13935

Copy link
Contributor

@schmikei schmikei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

disk.read.average Read rate KBps Average number of kilobytes read from the disk each second during the collection interval

net.bytesTx.average | Data transmit rate | KBps | Average amount of data transmitted per second

guestMemoryUsage MB

Validated values against my environment and all these are using the base 2 unit and since we are standardizing on UCUM, then we should use kibibytes and mebibytes to express these values in these units.

@BinaryFissionGames BinaryFissionGames marked this pull request as ready for review September 13, 2022 20:40
@djaglowski djaglowski merged commit 8f0d825 into open-telemetry:main Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants