This repository was archived by the owner on Nov 17, 2025. It is now read-only.
Span structure for messaging scenarios#220
Merged
carlosalberto merged 65 commits intoopen-telemetry:mainfrom Jun 29, 2023
Merged
Span structure for messaging scenarios#220carlosalberto merged 65 commits intoopen-telemetry:mainfrom
carlosalberto merged 65 commits intoopen-telemetry:mainfrom
Conversation
Loading
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This OTEP aims at defining consistent conventions about what spans to create for messaging scenarios, and at defining how those spans relate to each other. Instrumentors should be able to rely on a consistent set of conventions, as opposed to deducing conventions from a set of examples.
This was split from OTEP open-telemetry/opentelemetry-specification#192, which became too comprehensive.
Fixes open-telemetry/opentelemetry-specification#1085.