Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement OpenTracing Shim specifying custom propagators #3059

Merged
merged 8 commits into from
Mar 31, 2021

Conversation

malafeev
Copy link
Contributor

@malafeev malafeev commented Mar 24, 2021

Signed-off-by: Sergei Malafeev <[email protected]>
@carlosalberto
Copy link
Contributor

Left a few small comments. Overall LGTM. Thanks!

Signed-off-by: Sergei Malafeev <[email protected]>
Signed-off-by: Sergei Malafeev <[email protected]>
@carlosalberto
Copy link
Contributor

Left a pair of more small comments, but overall LGTM

@anuraaga @jkwatson if you guys could review this on a top-level fashion, just to be sure we are style-compatible, that would be great ;)

Signed-off-by: Sergei Malafeev <[email protected]>
Signed-off-by: Sergei Malafeev <[email protected]>
new TelemetryInfo(
getTracer(GlobalOpenTelemetry.getTracerProvider()),
GlobalOpenTelemetry.getPropagators()));
return createTracerShim(getTracer(GlobalOpenTelemetry.getTracerProvider()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any way here to actually use custom propagators. As far as I can see, we only every use the standard stuff in GlobalOpenTelemetry or the OpenTelemetry instance passed in directly. Are we missing a creational method here that will allow passing in custom OpenTracingPropagators somewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

Signed-off-by: Sergei Malafeev <[email protected]>
*
* @return a {@code io.opentracing.Tracer}.
*/
public static io.opentracing.Tracer createTracerShim(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 creational methods make me think we should be using a builder. any thoughts about that? It could definitely be done as a follow-up PR.

Copy link
Contributor Author

@malafeev malafeev Mar 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even 4.
maybe leave only two by removing createTracerShim(OpenTelemetry openTelemetry) and createTracerShim() ?
@carlosalberto ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call. Let's do that in a follow up. @malafeev would you mind creating an issue for that, so we don't forget, before merging this PR?

Copy link
Contributor Author

@malafeev malafeev Mar 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

created #3084

@carlosalberto carlosalberto merged commit 840e5cf into open-telemetry:main Mar 31, 2021
This was referenced Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants