Ariel Valentin

Yes. We currently run it with `--feature-gates service.noopTracerProvider` You can see in the profiles I attached the noopTracer is used: 

Here are profiles for 104 [profiles-104.tar.gz](https://github.com/user-attachments/files/16753916/profiles-104.tar.gz)

No worries @codeboten Something I may have not mentioned already, but my colleague @antonio had observed the latency regression as early as 105. We may downgrade to 105 and collect...

I have got some more for you here v0.107.4 [profiles-20240828.tar.gz](https://github.com/user-attachments/files/16785499/profiles-20240828.tar.gz) cc: @songy23

Thanks again for investigating. I am on the path to downgrade to 0.104.0 and will be eagerly awaiting the next release. Once it's out, I will deploy to a subset...

@bvsvas have you all had a chance to generate profiles? IIRC you all were not using OTTL so the latency you all reported would not be related to the transformers...

👋🏼 Is there a release schedule/project board handy I can subscribe to?

To elaborate here a bit we are missing docs on disabling or customizing instrumentation using environment variables. Right now, we only have it via configs. https://opentelemetry.io/docs/languages/ruby/libraries/#overriding-configuration-for-specific-instrumentation-libraries

The RubyDocs has a snippet that we should include on `opentelemetry.io`: https://rubydoc.info/gems/opentelemetry-instrumentation-base/0.22.3/OpenTelemetry/Instrumentation/Base > The instrumention class establishes a convention for disabling an instrumentation by environment variable and local configuration. An...

Cc: @rmosolgo