David Ashpole

One topic that came up during today's spec call is the idea of making this attribute's behavior consistent across exporters. For example, prometheus adds it as a prefix to metrics,...

I've opted to update the PR to use the prefix-less `short_name` instead of `scope.short_name` based on discussions above.

> @dashpole does the tooling works in this case, to auto generate the table? (without a prefix) I had to add one commit to the scope build-tools PR to allow...

> Why flatten in the first place, when OpenMetrics specifically describes the use of join? I don't think we should flatten for Prometheus/OpenMetrics. I've proposed a join-able info metric in...

Based on https://github.com/open-telemetry/opentelemetry-specification/pull/2703#issuecomment-1231892392, this isn't required anymore.

The prometheus metric would ideally be named `http_server_duration_seconds`, which is close to the expected naming for that metric in the prometheus ecosystem (`http_request_duration_seconds`, which is used [in the prometheus metric...

Yeah, a metric ending in `_ms` would be strange to prometheus users. Even spelling out `_milliseconds` would be better than `_ms`. Ideally, exporters would convert metrics in `ms` to `seconds`...

Scaling all sum + bucket boundaries seems like the best in the histogram case. The only case where I don't think it works correctly is for exponential histograms. IIUC, bucket...

One of the prometheus maintainers is working on support for exponential histograms in prometheus, but i'm not sure what the plan is or how far along they are. For now,...

> Are Scope attributes considered a completely different namespace from the other attributes? I.e. can I have a Scope attribute http.host that has a completely different meaning from the Span...