Handle storage metrics > 2GB #168
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For storage metrics over 2GB, the limit of a 32-bit signed integer is reached, so MongoDB returns the value as a bigint. OpenTelemetry metrics doesn't support bigint, so it just omit those metrics, resulting in no reported value.
This change forces conversion of these metrics to a number. We should not get any loss of precision in any realistic metric values, since
numbercan still accurately store values up to 2^53-1.