Francis Bogsanyi

> But that would make a client span to be child of a client span which I do not even know if it is legal That is now officially allowed,...

I'm no expert in Faraday, but I believe you can manually add the Faraday tracing middleware wherever you want in the middleware chain, and the instrumentation will detect that and...

https://github.com/open-telemetry/opentelemetry-specification/issues/259 metrics SDK spec moved to Alpha 0.3, so moving the exporter as well.

We don’t yet have an implementation of Metrics in the SDK. We need that before we can start work on a Prometheus (or statsd) exporter.

Thanks for the bug report @thomasLeclaire. I think the problem goes a little deeper than this, and I'd like us to fix the root cause. We are not only ignoring...

Hi @keiko713. The main outstanding issue with that PR is exactly what you've addressed here. See https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/529#discussion_r1355160854. I'd really appreciate it if you could port your fix to that PR....

Sadly, the fix here is "configure OpenTelemetry _after_ forking". Reconfiguring is hard-or-unsupported, IIRC. 🤔

Assuming you have some kind of `after_fork` hook available in your application framework (e.g. in Rails, Unicorn, Puma, Resque, etc.), then you can do something like: ```ruby OpenTelemetry.tracer_provider = OpenTelemetry::SDK::Trace::TracerProvider.new(...

We're updating a couple of attributes (`process.pid` and `yjit_resumed`) after forking, including after [re-forking](https://github.com/Shopify/pitchfork). We added a helper to our wrapper gem: ```ruby # Updates the global resource with the...

> I'll close, thanks Bogs. 😞 I was kinda hoping you'd fix the test and then we could fix the implementation 😄