According to https://opentelemetry.io/docs/specs/otel/metrics/sdk/#aggregation is should be possible to add a View to an Instrument and define how that View translates that Instrument to an Histogram. In particular, the defined Boundaries in the View should be used instead of the default histogram boundaries.
That does not seem to work at all.
If I understand the code correctly, then instrument created with kind histogram will not honor the view settings at all.
This has also been discussed to other languages, e.g.:
If I do this:
otel_meter_server:add_view(#{instrument_kind => ?KIND_HISTOGRAM},
#{aggregation_options =>
#{boundaries => [0.0, 1.1, 2.2, 4.4, 8.8]}}),
?create_histogram('meter1', #{description => <<"Meter 1">>, unit => us}),
then the the created histogram should have the boundaries defined by the view, but instead it will have the ?DEFAULT_BOUNDARIES.
According to https://opentelemetry.io/docs/specs/otel/metrics/sdk/#aggregation is should be possible to add a View to an Instrument and define how that View translates that Instrument to an Histogram. In particular, the defined Boundaries in the View should be used instead of the default histogram boundaries.
That does not seem to work at all.
If I understand the code correctly, then instrument created with kind
histogramwill not honor the view settings at all.This has also been discussed to other languages, e.g.:
boundariesoption inHistogramOptionsopentelemetry-js#2999 (comment)If I do this:
then the the created histogram should have the boundaries defined by the view, but instead it will have the ?DEFAULT_BOUNDARIES.