You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Segment not propgated when subsegment metadata is sufficiently long #415
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.
changed the title [-]Segment not propgated when subsegment metadata is a query string[/-][+]Segment not propgated when subsegment metadata is a query-like string[/+]on Nov 14, 2023
changed the title [-]Segment not propgated when subsegment metadata is a query-like string[/-][+]Segment not propgated when subsegment metadata is sufficiently long[/+]on Nov 15, 2023
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?
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?
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
Activity
[-]Segment not propgated when subsegment metadata is a query string[/-][+]Segment not propgated when subsegment metadata is a query-like string[/+][-]Segment not propgated when subsegment metadata is a query-like string[/-][+]Segment not propgated when subsegment metadata is sufficiently long[/+]mxiamxia commentedon Nov 17, 2023
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 commentedon Nov 18, 2023
Hi @mxiamxia, sure -- I will get back next, next week (I am away this coming week). Thank you so much for getting back.
yogabbagabb commentedon Nov 18, 2023
@mxiamxia
These are the logs:
yogabbagabb commentedon Nov 29, 2023
@mxiamxia
Just sending a ping :)