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.

Sign up for GitHub

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

Remove the need to maintain third party propagators. #1144

Merged
merged 6 commits into from
Nov 12, 2020
Merged

Remove the need to maintain third party propagators. #1144

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
cb76f33
Remove the need to mantain third party propagators.
carlosalberto Oct 26, 2020
2009fa3
Update the docs to be more liberal.
carlosalberto Nov 11, 2020
c116ac4
Merge branch 'master' into update_third_party_props
carlosalberto Nov 11, 2020
929b008
Update specification/context/api-propagators.md
carlosalberto Nov 11, 2020
d9d04a6
Update specification/context/api-propagators.md
carlosalberto Nov 11, 2020
9379410
Remove the mention of XRay propagator.
carlosalberto Nov 11, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 2 additions & 13 deletions specification/context/api-propagators.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,19 +320,8 @@ organization and MUST be distributed as OpenTelemetry extension packages:
* [Jaeger](https://www.jaegertracing.io/docs/latest/client-libraries/#propagation-format).

Additional `Propagator`s implementing vendor-specific protocols such as AWS
X-Ray (Note, AWS is used as an example, not as a requirement) trace header
protocol can be either maintained and distributed by their respective vendors or
as part of the OpenTelemetry organization. The reasons for maintaining those as
a community are:

- Propagators are small pieces of code and their functionality is often publicly
documented (unlike exporters).
- People will often need to use propagators that are not specific to their
tracing or metrics vendor. For example, customers of tracing vendor may still
want to use an Cloud vendor-specific propagator for requests to the services
of this cloud vendor.
- Only a small number of propagators will need to exist, and this number will
shrink as vendors and users shift to W3C TraceContext.
X-Ray trace header protocol MUST NOT be maintained or distributed as part of
the Core OpenTelemetry repositories.

### B3 Requirements

Expand Down