Rails tracing produces duplicate mysql2 spans

[mmarinaccio]

Current behaviour
After upgrading to version 2.2.0 of this gem, I'm now seeing duplicate mysql spans for my Rails application. It seems that both active_record and mysql2 components are producing redundant traces. I've tried disabling them but it they continue to appear.

Expected behaviour
A single mysql2 span for each mysql2 request made in my app process.

Steps to reproduce

How does datadog help you?
My team and I benefit immensely from Datadog observability! Quick debugging, performance optimization and proactive alerting.

Environment

• datadog version: 2.2.0
• Configuration block (Datadog.configure ...):

require 'datadog'

Datadog.configure do |c|
  c.env = Rails.env
  c.tracing.enabled = Rails.application.config.datadog_enabled

  # activate rails and framework configuration - https://docs.datadoghq.com/tracing/setup/ruby/#library-compatibility
  c.tracing.instrument :rails, enabled: true
  c.tracing.instrument :redis, enabled: true
  c.tracing.instrument :sidekiq, enabled: true, service_name: 'loyalsnap-sidekiq'
  c.tracing.instrument :rest_client, enabled: true, service_name: 'loyalsnap-rest-client'
  c.tracing.instrument :mysql2, enabled: false
  c.tracing.instrument :active_record, enabled: false
end

• Ruby version: 3.3.3
• Operating system: Ubuntu 22.04.4 LTS
• Relevant library versions: Rails 6.1.7.7

[gtrias]

Did you found how to fix it? We're facing the same issue with the mysql2 integration

[mmarinaccio]

Did you found how to fix it? We're facing the same issue with the mysql2 integration

@gtrias Sadly, no. I never figured it out and since moved onto other things. I just upgraded from Rails 6 to 7. Maybe that will make a difference. I'll try again soon and post back.