Segment not propgated when subsegment metadata is sufficiently long

[yogabbagabb]

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.

[mxiamxia]

Technically, X-Ray metadata attributes are able to store large size values. Can you follow the instruction below to enable debug log for XRay Daemon and share the related logs?

https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon-configuration.html

[yogabbagabb]

Technically, X-Ray metadata attributes are able to store large size values. Can you follow the instruction below to enable debug log for XRay Daemon and share the related logs?

https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon-configuration.html

Hi @mxiamxia, sure -- I will get back next, next week (I am away this coming week). Thank you so much for getting back.

[yogabbagabb]

@mxiamxia

These are the logs:

2023-11-18T19:23:16Z [Info] Initializing AWS X-Ray daemon 3.3.9
2023-11-18T19:23:16Z [Debug] Listening on UDP 0.0.0.0:2000
2023-11-18T19:23:16Z [Info] Using buffer memory limit of 78 MB
2023-11-18T19:23:16Z [Info] 1248 segment buffers allocated
2023-11-18T19:23:16Z [Debug] Using proxy address: 
2023-11-18T19:23:16Z [Debug] Fetch region eu-west-1 from environment variables
2023-11-18T19:23:16Z [Info] Using region: eu-west-1
2023-11-18T19:23:16Z [Debug] ARN of the AWS resource running the daemon: 
2023-11-18T19:23:16Z [Debug] No hostname set for telemetry records
2023-11-18T19:23:16Z [Debug] No Instance Id set for telemetry records
2023-11-18T19:23:16Z [Debug] Using Endpoint: https://xray.eu-west-1.amazonaws.com
2023-11-18T19:23:16Z [Debug] Telemetry initiated
2023-11-18T19:23:16Z [Info] HTTP Proxy server using X-Ray Endpoint : https://xray.eu-west-1.amazonaws.com
2023-11-18T19:23:16Z [Debug] Using Endpoint: https://xray.eu-west-1.amazonaws.com
2023-11-18T19:23:16Z [Debug] Batch size: 50
2023-11-18T19:23:16Z [Info] Starting proxy http server on 0.0.0.0:2000
2023-11-18T19:23:39Z [Debug] Received request on HTTP Proxy server : /GetSamplingRules
2023-11-18T19:24:16Z [Debug] Skipped telemetry data as no segments found

[yogabbagabb]

@mxiamxia

Just sending a ping :)