-
Notifications
You must be signed in to change notification settings - Fork 264
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
Allow sum
to present with negative measurements in Histogram
#303
Comments
There could be finer-grain statements people might like to specify about their instruments, like a range between [0, 100] for example, so maybe we'll find other solutions. If the definition for |
Referring to the contents of open-telemetry/oteps#156, there are three semantics for the Sum field of a Histogram, corresponding with a Histogram of values to synchronous Counter, UpDownCounter, and Gauge API events, where the sum is:
This suggests an enum value with three states, indicating which of the primitive instruments the measurements in the histogram semantically correspond with. |
Taken together with #308, the pair of proposals to me suggest a new field that contains extra semantic bits, two states for Count being monotonic or not, and three states for Sum being monotonic, non-monotonic, or non-meaningful. |
Fixes open-telemetry#303 - Add a new enumeration to Histogram denoting the type of sum for that histogram. - Update documentation to denote this new enumeration is used for interpretataion of the sum field. - Default the value of this enumeration to "monotonic sum" for backwards compatiblity.
Follow on to #187 - We currently limit the sum field in Histogram to be 100% compatible with OpenMetrics/Prometheus histograms so we know we can do a conversion when it exists. However, we think there's value to having sum available when there are negative measurements as well.
Tentative proposal:
The text was updated successfully, but these errors were encountered: