Segment not propgated when subsegment metadata is sufficiently long
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- observability-sre
Research direction
Start by running the supplied segment and subsegment metadata reproduction with the 882-character value, then compare it with the 30-character and trivial values. Trace how the Python SDK serializes and sends subsegment metadata to the X-Ray daemon; done means the long metadata value no longer prevents the segment from being forwarded.
Written by the indexing model from the issue text.
Description
The xray-daemon does not propagate a segment to AWS, where metadata is set using query, where query is both defined and used below:
query="******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************"
xray_recorder.begin_segment("segment")
c=xray_recorder.begin_subsegment("foo")
c.put_metadata("bar", query)
xray_recorder.end_subsegment()
xray_recorder.end_segment()
query is, above, a 882-character long string.
By contrast, if I set query to something trivial like "bla" then the xray-daemon forwards the segment. If I set query to a shorter 30-character string like "******************************", then the daemon forwards the segment.
There should be no problem with query being very long.
- Dominant language
- Python
- Stars
- 339
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-xray-sdk-python
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
aws/aws-xray-sdk-python#490 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 1/100
aws/aws-xray-sdk-python#460 ·
-
Next release Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
aws/aws-xray-sdk-python#457 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
aws/aws-xray-sdk-python#453 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aws/aws-xray-sdk-python#452 · 1 reaction ·
All issues in aws/aws-xray-sdk-python
Similar issues
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 62/100
inmanta/inmanta-core#10835 ·
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Diaoul/subliminal#1382 ·