From b0fc38cc3468654c1515fc630240cd4e4dd9ecc8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Fri, 22 Nov 2024 13:02:24 +0100 Subject: [PATCH] Remove semantic convention from Call Stack Span Association --- specification/behaviors.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/specification/behaviors.md b/specification/behaviors.md index c082590..dcc7f5c 100644 --- a/specification/behaviors.md +++ b/specification/behaviors.md @@ -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