[Metrics SDK] Change boundry type to double
for Explicit Bucket Histogram Aggregation, and change default bucket range
#1626
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.
Fixes: #1628, #1629
Irrespective of the aggregation data type (
long
ordouble
) for values stored in buckets, the boundaries range should be always of typedouble
.As mentioned in the specs - https:/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#explicit-bucket-histogram-aggregation
This PR fixes it.
Also, change the default buckets as per specs changes - open-telemetry/opentelemetry-specification#2770 from
0, 5, 10, 25, 50, 75, 100, 250, 500, 1000
to0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000