Robert

> Would it be possible to merge this and cut a beta release of this? I'd like to start experimenting w/ using it in my app. Hey @johnnyshields, I'm in...

FYI @johnnyshields you can track the discussions and progress around the rails instrumentation on this PR here https://github.com/open-telemetry/opentelemetry-ruby/pull/454

Hey @johnnyshields that would be awesome, let's do it in the Rails instrumentation gem.

> I was wondering if this was already explored. I'm happy to see this is planned. > But I wonder if doing Module#prepend on ActiveRecord subclasses isn't redundant with subscribing...

Racecar uses rdkafka once https://github.com/open-telemetry/opentelemetry-ruby/issues/919 is complete I intend to close this out as the instrumentation will be covered by including rdkafka instrumentation.

@dazuma could I trouble you to give this PR a look? https://github.com/googleapis/google-api-ruby-client/pull/3414

Hey @jcarres-mdsol, I've tried to recreate this with a new rails `6.0` project. My opentelemetry configuration. ```rb require 'opentelemetry/sdk' require 'opentelemetry/exporter/jaeger' require 'opentelemetry-instrumentation-mysql2' require 'opentelemetry-instrumentation-rails' OpenTelemetry::SDK.configure do |c| c.use_all c.service_name...

>This application indeed has background workers but I think these statements happen from the rails app because I was sending http requests to the API provided by that app and...

@jcarres-mdsol thank you for the update and sharing your findings. This is very similar to something I'm working on in regards to `sidekiq` and the `sidekiq-scheduler` gem that is producing...

Hey @indrekj thanks for opening the issue. We're looking at noisy/long traces internally as well and we can point at `instantiation` as one of the culprits. How receptive would you...