Well, in this particular case I do not fully agree with the solution. telemetry is meant to be low-level, minimal-overhead library for gathering metrics and traces. In this exact case it feels that it should be direct dependency just like you are using Logger. In the end telemetry is just additional logging toolkit. So while article premise is something I agree 100%, then I do not really agree with the example used in the article.

There should never be more than one reason for a class to change.

There should never be more than one party interested in modifying a unit of code.

Conway’s Law at work!