Joshua MacDonald

> moving in the opposite direction +1 This is why I changed my opinion, splitting metrics when they ought to be part of a single row in a multi-variate representation...

I would propose to see OTLP version information at the top-level of the structs passed to the collector. Appearing at the top-level of a struct makes it relatively simple for...

From [CNCF Slack](https://cloud-native.slack.com/archives/C01NPAXACKT/p1649112027764589?thread_ts=1649092404.096269&cid=C01NPAXACKT) we have a use-case described: > if the CRD is present then it is denoted by 1 as the metric value and if it's not (if it's...

This is a top priority (IMO) and I will begin working on the (very straightforward) proposal in the coming few weeks.

^^^ Here is the prototype I am working with,.

I would like to re-phrase this feature request: Can we allow deleting or unregistering Callbacks? For discussion in the Tuesday Jan 25 8AM PT Spec SIG.

There is a connected topic discussed in https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/supplementary-guidelines.md#asynchronous-example-attribute-removal-in-a-view The question is how, if at all, should an SDK know to stop reporting a metric?

To clarify my intention, I believe #2317 narrowly solves this problem stating the SDK SHOULD give applications a way to create callbacks that support being unregistered, which allows a user...

I worry about lock ordering and the potential for deadlock when I read this proposal, though I agree that using the stop-time field as an indicator for completed spans is...

I would extend this issue even further to support indefinite-lifetime spans. I would like to be able to start a span that never ends, and yet I would like to...