-
Notifications
You must be signed in to change notification settings - Fork 276
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
Clarify when bucket_counts array may be empty #619
Clarify when bucket_counts array may be empty #619
Conversation
The current definition says: "The number of elements in bucket_counts array must be by one greater than the number of elements in explicit_bounds array." However, it also says "bucket_counts is an optional field", which means its length can be 0, which than in turn means the length of explicit_bounds must be -1, which is impossible. We clarify that it is a valid situation to have both bucket_counts and explicit_bounds arrays empty.
Does this resolve open-telemetry/opentelemetry-specification/issues/3848? Should it be solved first? I am always unsure about the exact relationship between the proto and the data model |
@mx-psi this PR is only about the regular Histogram. open-telemetry/opentelemetry-specification#3848 is about Exponential Histogram. |
Ah, my bad, sorry |
CC @open-telemetry/specs-metrics-approvers |
This was open for several days and appears to match the data model spec. Merging. |
The current definition says:
"The number of elements in bucket_counts array must be by one
greater than the number of elements in explicit_bounds array."
However, it also says "bucket_counts is an optional field", which
means its length can be 0, which then in turn means the length of
explicit_bounds must be -1, which is impossible.
We clarify that it is a valid situation to have both bucket_counts and explicit_bounds arrays empty.