[bp/1.27] datadog: fix names in Span::spawnChild#31593
Merged
phlax merged 2 commits intoenvoyproxy:release/v1.27from Jan 4, 2024
Merged
Conversation
Signed-off-by: David Goffredo <david.goffredo@datadoghq.com>
phlax
reviewed
Jan 3, 2024
Member
phlax
left a comment
phlax
left a comment
There was a problem hiding this comment.
@dgoffredo could you please include the changelog - its even more important on the release branches
Signed-off-by: David Goffredo <david.goffredo@datadoghq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is a backport of #31366 onto the v1.27 release branch.
These changes fix a bug in the Datadog tracing extension. Previously,
Span::spawnChildwould produce spans whose "operation name" had the value of what should instead be the "resource name." With these changes, setting the "operation name" sets the "resource name" instead, and the "operation name" is always the hard-coded value "envoy.proxy".