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

Move opencensus binary propagation to contrib #467

Merged
merged 3 commits into from
Nov 30, 2020

Conversation

dashpole
Copy link
Contributor

@dashpole dashpole commented Nov 24, 2020

Issue: open-telemetry/opentelemetry-go#93

This was originally added to opentelemetry-go in open-telemetry/opentelemetry-go#1334, but we decided it should be moved to contrib.

This copies the binary propagation, and adds a new go module so that opencensus dependencies aren't added to users of other propagation formats.

@dashpole dashpole changed the title ove opencensus binary propagation to contrib Move opencensus binary propagation to contrib Nov 24, 2020
@dashpole dashpole force-pushed the opencensus_binary_move branch 2 times, most recently from 88132c1 to 14d656e Compare November 24, 2020 18:13
propagators/opencensus_binary/go.mod Outdated Show resolved Hide resolved
propagators/opencensus_binary/binary.go Outdated Show resolved Hide resolved
@MrAlias MrAlias merged commit f9f5a21 into open-telemetry:master Nov 30, 2020
@dashpole dashpole deleted the opencensus_binary_move branch November 30, 2020 21:08
plantfansam referenced this pull request in plantfansam/opentelemetry-go-contrib Mar 18, 2022
* Remove binary propagators

They are in process of being dropped from the specification and we
haven't be using them anywhere in the project. Can reintroduce them
later.

* Rename Supplier to HTTPSupplier

The supplier is used only in HTTP propagators currently. It's not
clear if it will be useful for binary propagators if they get to be
specified at some point.

* Rework propagation interfaces

The biggest change here is that HTTP extractors return a new context
with whatever information the propagator is able to retrieve from the
supplier. Such interface does not hardcode any extractor's
functionality (like it was before by explicitly returning a span
context and correlation context) and makes it easy to chain multiple
propagators.

Injection part hasn't changed.

* Add Propagators interface

This interface (and its default implementation) is likely going to be
the propagation API used the most. Single injectors, extractors or
propagators are likely going to be used just as parameters to the
Option functions that configure the Propagators implementation.

* Drop noop propagator

It's rather pointless - just create an empty Propagators instance.

* Fix wrong name in docs

Co-authored-by: Joshua MacDonald <[email protected]>
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