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

Jump to bottom

specify that resources map to jaeger process tags #891

Merged
merged 4 commits into from
Sep 1, 2020
Merged

specify that resources map to jaeger process tags #891

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a5e17ba
specify that resources map to jaeger process tags
mwear Aug 26, 2020
56fb9c5
add changelog entry
mwear Aug 26, 2020
85fc7d7
be less prescriptive on handling multiple resources
mwear Aug 27, 2020
6c3cee6
Merge branch 'master' into jaeger_resources
bogdandrutu Sep 1, 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
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ release.

New:

- Define resource mapping for Jaeger exporters
([#891](https://github.com/open-telemetry/opentelemetry-specification/pull/891))
- Add resource semantic conventions for operating systems
([#693](https://github.com/open-telemetry/opentelemetry-specification/pull/693))
- Clarification of the behavior of the Trace API, re: context propagation, in
Expand Down
6 changes: 6 additions & 0 deletions specification/trace/sdk_exporters/jaeger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,12 @@ TBD
This section discusses the details of the transformations between OpenTelemetry
and Jaeger.

### Resource

OpenTelemetry resources MUST be mapped to Jaeger process tags. Multiple resources can exist for a
single process and exporters need to account for this by grouping spans by resource, and exporting
them in batches.
mwear marked this conversation as resolved.
Show resolved Hide resolved

### InstrumentationLibrary

OpenTelemetry Span's `InstrumentationLibrary` MUST be reported as span `tags` to Jaeger using the following mapping.
Expand Down