HaloFour

> It looks like the async instruments from OTEL may need more machinery to work correctly here. I see, that was my misunderstanding. I assumed that the callback would hold...

> Baggage != exemplars. baggage is the ability to attach labels (dynamically) via distributed context propagation. Right, in that case we can just treat them like `Attributes` and mix them...

@anuraaga > Just curious, is there a reason to have an SDK that implements the OTel metrics API using micrometer, instead of the other way around, a micrometer registry that...

I believe that the bridge is still needed as there will be projects that need to make use of both facades and Micrometer is already more established, especially in Spring...

> Would it help you to have the ability to disable writing a default `event.dataset` so that the value from MDC is the only one? Yes, this would work. Thanks!...

@rdifrango > I also would like to see this feature and I wonder if there's a way to tap into the existing capabilities of logback and log4j2 as they already...

Thanks for opening this issue! I was already exploring what would be involved in making Money an implementation of OpenTelemetry by either implementing the OpenTelemetry API interfaces directly or by...

Changes to spans: 1. Allow updating of span name 2. Allow stopping a span with an end timestamp 3. Expand supported `Note[T]` types to include String, Long, Double and Boolean...

> I wonder if money can directly implement any open-telemetry API / interface(s) as well? In other words, abandon what money has in it's own java interfaces, and substitute with...

I can start on a WIP PR that has the Money interfaces extend from the OTel interfaces and see where that lands. More spaghetti at the wall, maybe we can...