Skip to content
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

Adding segment splits #111

Merged
merged 1 commit into from
Oct 11, 2023

Conversation

atshaw43
Copy link

Description:
We are adjusting the segment creation to accommodate local root spans.

If a span is a not a local root, then we keep existing behavior.
If it is a local root then:

If it is an Internal or Server span, then promote it to a segment.
Else we will split it into a segment and subsegment. The segment will represent the service operation and the subsegment will represent the dependency (service A calls service B).
Testing:
Unit Testing

Documentation:
None

@lisguo
Copy link

lisguo commented Oct 11, 2023

Can we rerun the check load-tests / loadtest (TestBallastMemory|TestLog10kDPS) (pull_request) Failing after 4m? this shouldn't be failing...the others are known issues it seems.

@lisguo
Copy link

lisguo commented Oct 11, 2023

I re-ran the job, it looks good to me

@lisguo lisguo merged commit 5b46fae into amazon-contributing:aws-cwa-dev Oct 11, 2023
74 of 78 checks passed
lisguo pushed a commit to lisguo/opentelemetry-collector-contrib that referenced this pull request Oct 20, 2023
andrzej-stencel pushed a commit to open-telemetry/opentelemetry-collector-contrib that referenced this pull request May 22, 2024
**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
Cherry-picking from downstream:

amazon-contributing#111

amazon-contributing#115

amazon-contributing#127

- We are adjusting the segment creation to accommodate local root spans.
  If a span is a not a local root, then we keep existing behavior.
  If it is a local root then:
    - If it is an Internal or Server span, then promote it to a segment.
Else we will split it into a segment and subsegment. The segment will
represent the service operation and the subsegment will represent the
dependency (service A calls service B).
- Update the common logic for setting segment.Name, which previously
only looked at CLIENT/PRODUCER spans, to also look at CONSUMER spans.

**Link to tracking Issue:** <Issue number if applicable>

**Testing:** <Describe what testing was performed and which tests were
added.>
Unit Testing

**Documentation:** <Describe the documentation added.>

---------

Co-authored-by: atshaw43 <[email protected]>
Co-authored-by: Thomas Pierce <[email protected]>
Co-authored-by: John Knollmeyer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants