The Wayback Machine - https://web.archive.org/web/20201023183158/https://github.com/ory/hydra/issues/2130
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support AWS X-Ray as distributed trace #2130

Open
simpleway opened this issue Oct 13, 2020 · 1 comment
Open

Support AWS X-Ray as distributed trace #2130

simpleway opened this issue Oct 13, 2020 · 1 comment

Comments

@simpleway
Copy link

@simpleway simpleway commented Oct 13, 2020

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
Copy link
Member

@aeneasr aeneasr commented Oct 20, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.