You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All histogram metrics currently are using same predefined buckets values, that makes most of them unusable due to buckets being disproportional to observed values. With current version of otel it is only possible to set buckets values on global meter, but given different nature of each histogram it makes it unusable.
Implementation ideas
All histogram metrics currently are using same predefined buckets values, that makes most of them unusable due to buckets being disproportional to observed values. With current version of otel it is only possible to set buckets values on global meter, but given different nature of each histogram it makes it unusable.
This is known issue of otel and tracked in:
open-telemetry/opentelemetry-go#3826.
API spec improvement has been suggested and merged in:
open-telemetry/opentelemetry-specification#3216
Implimentation is still to be done. And tracked in:
open-telemetry/opentelemetry-go#4094
Once support of bucket boundary metric advice support is implemented in otel we need to add custom bucket per each histogram.
The text was updated successfully, but these errors were encountered: