feat(core): Deprecate spanId
on propagationContext
#14482
Merged
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 PR deprecates setting & reading the
spanId
on the propagation context, as well asgeneratePropagationContext()
.Instead, you can/should now omit the spanId:
scope.setPropagationContext({ traceId: generateTraceId() })
, which will under the hood generate a new random span ID for the time being.This PR does not change any behavior about using the spanId, but adds comments for where we want to replace this in v9 - there, we'll just generate new span IDs on the fly in these cases instead of using the one from propagation context. The propagation context will only hold traceId & parentSpanId (optionally).
Closes #14255