Joshua MacDonald

> This is only a conflict if they will exist in the same data stream. I see. I think it would help me to see an end-to-end implementation that uses...

Reviewers, there was a [recent change in the specification.](https://github.com/open-telemetry/opentelemetry-specification/pull/2633) This applies the corresponding change to the public exponential histogram mapping functions. PTAL.

(Will be a few days before this is updated.)

~LowerBoundary() needs to be exact to match the the mapping function, will resolve.~ EDIT: resolved.

There are several questions and answers here. ---- OpenTelemetry Metrics is explicitly moving away from instruments named for the action they perform, and moving toward instruments named for how they...

I have feelings. https://github.com/open-telemetry/opentelemetry-proto/issues/81

This could use the format embraced by Prometheus for the boundaries as "le" labels. The upper boundary at 1 is encoded as a label "le=1" in this scheme.

This will be important before we can vary the collection interval on a per-instrument basis. OTOH doesn't feel urgent to me.

I created https://github.com/open-telemetry/prometheus-sidecar

I made the repo private while I migrate commits. I've frozen the Lightstep repo and will begin that soon.