Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider not exposing `getActiveSpanProcessor` at `Tracer` level

See original GitHub issue

Although not clearly stated in the Specification, usually this functionality is only exposed at the TracerProvider level. Not a strong feeling though.

Issue Analytics

State:
Created 2 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

dyladancommented, Apr 22, 2021

Since carlos said he didn’t have a strong feeling and this is only an SDK concern, not API, I think it’s fine to close.

0reactions

Flarnacommented, Apr 22, 2021

The Tracer has a reference to it’s TracerProvider. We could pass it to the Span constructor. Or we add a public getter on class Tracer to get the TracerProvider instead the SpanProcessor.

But not sure if it is worth the effort.