-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/awsxray] Fix X-Ray Segment status code #24381
Merged
jpkrohling
merged 2 commits into
open-telemetry:main
from
mxiamxia:fix-xray-segment-status
Aug 2, 2023
Merged
[exporter/awsxray] Fix X-Ray Segment status code #24381
jpkrohling
merged 2 commits into
open-telemetry:main
from
mxiamxia:fix-xray-segment-status
Aug 2, 2023
Conversation
This file contains 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
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
from
July 19, 2023 04:00
b4f3641
to
0225315
Compare
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
2 times, most recently
from
July 19, 2023 04:12
c5672d7
to
5dae054
Compare
bjrara
reviewed
Jul 19, 2023
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
2 times, most recently
from
July 19, 2023 22:26
df7890f
to
c4c3f4a
Compare
LGTM |
bjrara
approved these changes
Jul 19, 2023
wangzlei
approved these changes
Jul 19, 2023
Hi @dashpole, could you please take a look this PR when you get a chance |
srprash
approved these changes
Jul 19, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with some nits.
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
from
July 19, 2023 23:53
c4c3f4a
to
aaf5c58
Compare
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
from
July 20, 2023 04:11
aaf5c58
to
f0cff2f
Compare
mxiamxia
force-pushed
the
fix-xray-segment-status
branch
from
July 21, 2023 20:32
bec1c24
to
21e9a64
Compare
mxiamxia
added a commit
to amazon-contributing/opentelemetry-collector-contrib
that referenced
this pull request
Jul 21, 2023
Hi @dashpole , kindly follow if you could help to take a look this PR. Ty! |
Hi can I get some help from @open-telemetry/collector-contrib-approvers to review this PR? |
TylerHelmuth
approved these changes
Jul 31, 2023
jpkrohling
changed the title
Fix X-Ray Segment status code
[exporter/awsxray] Fix X-Ray Segment status code
Aug 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
The conversion from HTTP spans to X-Ray segments did not accurately capture the HTTP status code during the translation of the cause. As a result, some failed HTTP requests with 4xx and 5xx status codes were displayed as having an "OK" status in the X-Ray console. Also, add remote attribute in Exception for X-Ray remote segments.
Link to tracking Issue:
N/A
Testing:
unit test
Documentation:
N/A