Skip to content

[exporter/awsxray] Add logic for stripping the AWS.SDK prefix for Local Root spans #33001

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.

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

Conversation

jj22ee
Copy link
Contributor

@jj22ee jj22ee commented May 11, 2024

Description:

Depends on PR (Shares the first 4 commits):

Cherry-picking from downstream:
amazon-contributing#127

Adding logic to strip AWS.SDK from local root dependency spans. This had been done previously for other spans, but there was a missed codepath related to local root naming. (Related previous change to strip the prefix in other cases 7c037ad)

Link to tracking Issue:

Testing:
Added a unit test

Documentation:

atshaw43 and others added 6 commits May 10, 2024 20:59
In this commit, we are fixing a couple small bugs missed in the previous review. First, we are adding a nil-guard when settting dependencySubsegment.Name, to avoid the (unlikely, but possible) scenario where local root dependency spans are created without awsRemoteService. Second, we are updating the common logic for setting segment.Name, which previously only looked at CLIENT/PRODUCER spans, but now needs to look at CONSUMER spans.
* Add logic for stripping the AWS.SDK prefix for Local Root spans

- Previous change to strip the prefix in other cases open-telemetry@7c037ad

* De-duplicate identical logic
@github-actions github-actions bot requested review from srprash and wangzlei May 11, 2024 05:18
@jj22ee jj22ee changed the title [exporter/awsxray] Adjust the segment creation [exporter/awsxray] Add logic for stripping the AWS.SDK prefix for Local Root spans May 13, 2024
@jj22ee jj22ee closed this May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants