search

typelevel / natchez

functional tracing for cats
MIT License
324 stars 79 forks source link

Natchez Xray Fails to Connect Requests from Service to Service #1002

Closed albin-kv closed 5 months ago

albin-kv commented 5 months ago

Problem: Natchez Xray isn't linking serivce-to-service HTTP requests smoothly with AWS Xray tracing, even though the AWS Xray tracer header is present.

wrong xray Although the trace id is the same, requests to another service shows up as another flow/tree(webdealer service hits /search endpoint in search service)

Impact: This messes up the AWS Xray UI, displaying disjointed request trees instead of a single flow. It's a headache for developers trying to troubleshoot and analyze request journeys.

Solution: We've identified and PR'ed a fix - #1001 . Enhancing Natchez Xray to recognize and use the AWS Xray tracer header properly will ensure seamless request tracing.

right xray Search service is now part of the webdealer flow after webdealer service hits /search endpoint.

Action: We kindly request the maintainers of Natchez to review our PR and consider integrating the proposed solution into the main codebase.

Thanks for your attention to this issue.

mpilquist commented 5 months ago

Thanks for the great writeup and PR!

Closed by #1001.