Josh Suereth
Josh Suereth
> Is also the [cloud.* semantic conventions](https://opentelemetry.io/docs/specs/semconv/resource/cloud/) in scope for this effort? Yes. Although, we're going to start with k8s resource stability, then likely host machine / VM.
Thanks @arminru !
Invitation sent!
Invitation Sent!
With the merging of [OTEP](https://github.com/open-telemetry/oteps/blob/main/text/0243-app-telemetry-schema-vision-roadmap.md) - We're be working on phase 1 of this. That means spending time formalizing a "resolved schema", specifically: > Upon implementation, the OpenTelemetry project's telemetry...
@tedsuo I think we still need it but I've put effort on hold to address higher-priority items. I think we still have time to revisit this post some semconv stability,...
`for` is the right name as we're using its Monadic usage. What you want, and what I'm trying to figure out how to do correctly, is something like: ``` scala...
Yes, we'd need to trampoline to fix this. Will leave this as an open implementation question for now. This library was not intended for such nested usage initially, but if...
Before merging this, can you take a look at #47 - Specifically how to handle the case where an exception is thrown in one of the threads and then what...
The more I think about it the more I'm hesitant on multi-threading features without more multi-threaded controls, especially if we don't know whether theunderlying resource is "concurrency safe"