Destringify APM tracer interface #94864
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.
Today the APM
Tracerinterface identifies each span by a raw string, but in practice there is structure to these strings: task-related spans have IDs liketask-NNNNand spans that relate to REST requests have IDs likerest-NNNN. This convention is distributed across the codebase a little too widely, so with this commit we centralise it into aSpanIdclass, and introduce specific overrides forTaskandRestRequestto avoid callers needing to construct IDs themselves.