How to support per unit bucket boundaries in v0.33.0?

[yux0]

Currently, we are on Go sdk v0.30.0 and implemented a customized aggregator selector to support per unit bucket boundaries. sample.

I am trying to upgrade to v0.33.0 and do not find a way to matchInstrumentUnit. Does it support of per unit bucket boundaries in v0.33.0?

[MrAlias]

In the new SDK this would be accomplished with a view.View, in theory. It is currently theoretical because that package does not support matching instrument units.

There is currently a proposal to refactor that views. The proposed replacement would allow you to accomplish matching an instrument unit and replacing histogram boundaries. Please leave a 👍 on the proposal if you would like to support its inclusion or any comment you have.

[yiminc]

@MrAlias , how to do per unit type custom histogram boundaries? The proposed change related to this requirement is to replace the view.View with a View func. The View func is defined as type View func(Instrument) (Stream, bool). However, the Instrument does not have unit info? So how to match based on unit?

[MrAlias]

The Instrument type would be defined to have a unit field: https://github.com/open-telemetry/opentelemetry-go/pull/3397/files#diff-2b58257199790c9227975e80f5f2122187de28546546271137da97e324be4782R80

[MrAlias]

I've updated the proposal issue to reflect this.