⁠NoopTracer warning in v1.73 affects test suites

[bastiankoetsier]

Hello!
Following the changes in PR #2991 (released in v1.7.3), the ⁠NoopTracer started logging a warning to encourage explicit tracer initialisation.
This change has had a noticeable impact on our testing workflow. Because we rely on the global tracer existing in many test scenarios, we now see this warning frequently, prompting us to add explicit ⁠mocktracer initialisations in tests where tracing isn't the primary focus. Ideally, a ⁠NoopTracer wouldn't produce log output.
Could we explore options to mitigate this? Reverting the warning for the ⁠NoopTracer or ensuring it remains silent when ⁠DD_TRACE_ENABLED is false would be very helpful for simplifying our test setups.
What are your thoughts on this?
Thanks!

[darccio]

Hi @bastiankoetsier. We'll release a version demoting the warning to debug. You can already pull it as v1.73.1-rc.1.

[darccio]

The fixed version was released as v1.73.1.