SimunKaracic

Sure, I can do that. But this isn't about making a workaround for me, but about improving the out of the box experience for ZIO-http. If we're gonna tell people...

Not reflection, but a javaagent, bringing significantly less of a runtime perf cost. And yes, they extract info not reachable by user code! But none of the code for this...

So this is why I'm asking for confirmation that some internal zio-http code, where the OTEL would hook into, won't change. The javaagent recognizes where to add that code based...

> It's similar to how Kamon instruments the ZIO runtime, via the Runtime.defaultSupervisor FiberRef That's exactly what [OTEL is doing](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/e853afe2c7de27268f5aec032ddbc8dfa9ad10e2/instrumentation/zio/zio-2.0/javaagent/src/main/java/io/opentelemetry/javaagent/instrumentation/zio/v2_0/ZioRuntimeInstrumentation.java#L28) > I think the functionality that @SimunKaracic is asking for...

> I am much more in favor of having built in metrics, spans, logs and whatever. If you provide built in spans/metrics in ZIO-http, that means your users have to...

My original idea was to provide a separate instrumentation module in the OTEL library, specifically for ZIO-http. No changes in ZIO-http. All that module would have to do, is hook...