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

[jaeger exporter] Document mapping of service name #1222

Merged
merged 5 commits into from
Nov 15, 2020
Merged

[jaeger exporter] Document mapping of service name #1222

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
195dacf
[jaeger exporter] Document mapping of service name
yurishkuro Nov 10, 2020
ca78597
Add to changelog
yurishkuro Nov 10, 2020
15c58ff
fix link
yurishkuro Nov 10, 2020
a7b4b31
try to fix the link
yurishkuro Nov 10, 2020
6ed3345
try to fix the link
yurishkuro Nov 10, 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:

- Document service name mapping for Jaeger exporters
([1222](https://github.com/open-telemetry/opentelemetry-specification/pull/1222))
- Add performance benchmark specification
([#748](https://github.com/open-telemetry/opentelemetry-specification/pull/748))
- Enforce that the Baggage API must be fully functional, even without an installed SDK.
Expand Down
6 changes: 5 additions & 1 deletion specification/trace/sdk_exporters/jaeger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,13 @@ and Jaeger.

### Resource

OpenTelemetry resources MUST be mapped to Jaeger process tags. Multiple resources can exist for a
OpenTelemetry resources MUST be mapped to Jaeger's `Span.Process` tags. Multiple resources can exist for a
single process and exporters need to handle this case accordingly.

Critically, Jaeger backend depends on `Span.Process.ServiceName` to identify the service
that produced the spans. That field MUST be populated from the `service.name` attribute
of the [`service` resource](../../resource/semantic_conventions/README.md#service).

### InstrumentationLibrary

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