David Elner

Cool! I think I'd like to incorporate this in then, some way, either using refinements or some other strategy. I'd advise implementing some kind of monkey patch with this in...

Hi @evanlok! Still having trouble? I might recommend upgrading to our latest 1.x version, which may include some improvements for this. (There would be some breaking changes in your configuration,...

Although I don't expect this will address the race condition explicitly, we have started to rewrite the behavior of the startup logger in this #3020. I think we need to...

Thanks for the heads up @rmosolgo . Indeed `ddtrace` does depend on `Thread.current` to store trace context; when this isn't available, or changes, then active traces will not cross execution...

@AlexRiedler We spent a bit of time looking into this. Last I remember (some time ago), Ractors themselves have been a bit unstable, not receiving widespread use, and there are...

@marcotc any updates on this? I know we saw this, not sure if we've made any progress on it.

> Did the Rails team provide any guidance on the most appropriate way to add instrumentation/tracing? @ioquatix No, but to be fair, the code is relatively old and I didn't...

Hey @dasch ! Happy to see you again in the repo. :) I think this is a great change; it's moving in the general direction of where we want to...

> Perhaps do a search for all cases where service_name gets defaulted on an integration level and do all of them in one go? @dasch that's exactly where we're leaning....

Also, slightly off topic, but just to pick your brain @dasch... Users often (mis)use the `service_name` on these integrations to make distinct layers (middleware, controllers, presentation) visible within their application....