Skip to content

docs(tracing) clarify span_id attribute #11997

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 3 commits into from
Dec 5, 2024
Merged

docs(tracing) clarify span_id attribute #11997

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8cdf134
Clarify span_id attribute
markushi Nov 29, 2024
d098349
Link TwP docs
markushi Nov 29, 2024
fe64298
Update develop-docs/sdk/data-model/event-payloads/contexts.mdx
markushi Nov 29, 2024
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: 1 addition & 1 deletion develop-docs/sdk/data-model/event-payloads/contexts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. 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"`

Expand Down