From 8cdf134d358a00982c449b91abc9b0fb41af0c68 Mon Sep 17 00:00:00 2001 From: Markus Hintersteiner Date: Fri, 29 Nov 2024 11:54:15 +0100 Subject: [PATCH 1/3] Clarify span_id attribute --- develop-docs/sdk/data-model/event-payloads/contexts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/data-model/event-payloads/contexts.mdx b/develop-docs/sdk/data-model/event-payloads/contexts.mdx index 8d21932524591..372732224b0e0 100644 --- a/develop-docs/sdk/data-model/event-payloads/contexts.mdx +++ b/develop-docs/sdk/data-model/event-payloads/contexts.mdx @@ -628,7 +628,7 @@ Additional information that allows Sentry to connect multiple transactions, span `span_id` -: _Required_. The ID of the span. +: _Required_. The ID of the span or transaction. If there's none available (e.g. in tracing without performance mode), a random span ID must be provided. - Example: `"bb8f278130535c3c"` From d09834929815fc4fd8fbb2cb2b86a4e00af33933 Mon Sep 17 00:00:00 2001 From: Markus Hintersteiner Date: Fri, 29 Nov 2024 18:08:50 +0100 Subject: [PATCH 2/3] Link TwP docs --- develop-docs/sdk/data-model/event-payloads/contexts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/data-model/event-payloads/contexts.mdx b/develop-docs/sdk/data-model/event-payloads/contexts.mdx index 372732224b0e0..f3d3275fffc57 100644 --- a/develop-docs/sdk/data-model/event-payloads/contexts.mdx +++ b/develop-docs/sdk/data-model/event-payloads/contexts.mdx @@ -628,7 +628,7 @@ Additional information that allows Sentry to connect multiple transactions, span `span_id` -: _Required_. The ID of the span or transaction. If there's none available (e.g. in tracing without performance mode), a random span ID must be provided. +: _Required_. The ID of the span or transaction. If there's none available (e.g. in tracing without performance mode), a random span ID must be provided. [See the TwP docs](/sdk/telemetry/traces/tracing-without-performance/#attaching-trace-data-to-events-and-envelopes) for more details. - Example: `"bb8f278130535c3c"` From fe642982802b632a4d9a1acb3299dfb2804d04f3 Mon Sep 17 00:00:00 2001 From: Markus Hintersteiner Date: Fri, 29 Nov 2024 18:17:07 +0100 Subject: [PATCH 3/3] Update develop-docs/sdk/data-model/event-payloads/contexts.mdx Co-authored-by: Luca Forstner --- develop-docs/sdk/data-model/event-payloads/contexts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/data-model/event-payloads/contexts.mdx b/develop-docs/sdk/data-model/event-payloads/contexts.mdx index f3d3275fffc57..97e71e0f258f8 100644 --- a/develop-docs/sdk/data-model/event-payloads/contexts.mdx +++ b/develop-docs/sdk/data-model/event-payloads/contexts.mdx @@ -628,7 +628,7 @@ Additional information that allows Sentry to connect multiple transactions, span `span_id` -: _Required_. The ID of the span or transaction. If there's none available (e.g. in tracing without performance mode), a random span ID must be provided. [See the TwP docs](/sdk/telemetry/traces/tracing-without-performance/#attaching-trace-data-to-events-and-envelopes) for more details. +: _Required_. The ID of the span or transaction. For non-transaction events, and if performance monitoring is disabled, it may still be desired to attach events to a trace via a trace ID. In these cases, you still need to provide a span ID. This span ID can effectively be entirely random and doesn't need to relate to an actual span, however, it is recommended to consider using the same span ID for multiple events within the same unit-of-execution (e.g. a request). [See the TwP docs](/sdk/telemetry/traces/tracing-without-performance/#attaching-trace-data-to-events-and-envelopes) for more details. - Example: `"bb8f278130535c3c"`