Skip to content

Remove semantic convention from Call Stack Span Association #324

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

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Remove semantic convention from Call Stack Span Association #324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 0 additions & 4 deletions specification/behaviors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,6 @@ MUST be able to associate the call stack to the span. This association SHOULD
happen as close to the sampling point as feasible, but MAY occur later in a
processing pipeline.

After the association has been made, the `TraceId` and `SpanId` fields of the
[LogRecord message](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/logs/v1/logs.proto)
MUST be populated (see [here](semantic_conventions.md#logrecord-message-fields)).

### Call Stack Ingest

Call stacks MUST be ingested as [OpenTelemetry
Expand Down