Support AWS X-Ray as distributed trace

[simpleway]

Is your feature request related to a problem? Please describe.

AWS Fargate and ECS is a popular container cluster. Jaeger and datadog are not native to AWS, require additional setup, cost and operations. AWS X-Ray support distributed tracing for ECS and AWS lambda. A custom lambda can be developed for oauth2 token validation against Hydra. Currently tracing between lambda authorizer and hydra go to separate places, X-Ray and Jaeger.

Describe the solution you'd like OpenCensus support export to AWS X-Ray: https://opencensus.io/exporters/supported-exporters/go/xray/. Now OpenTracing and OpenCensus are merged to OpenTelemetry. It will be nice to hydra support tracing to AWS X-Ray, so tracing lambda authorizer and hydra can be displayed in single place: X-Ray.

[aeneasr]

Sorry for the late reply, sounds like a good idea! Would you be open to contribute that?

[simpleway]

Sorry for late response. I'm new to golang, might take a while to get comfortable with. But I'd like to contribute, any guidelines of this project to follow?

[aeneasr]

Contributing guidelines can be found here: https://github.com/ory/hydra/blob/master/CONTRIBUTING.md

But other than that just give it a go :)

[aeneasr]

It's possible that you need to change something in https://github.com/ory/x

[driverpt]

This can be done in the scope of #2597 , since AWS has AWS OTEL Collector which natively integrates with XRay

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️