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 for OpenTracing #281

Closed
kevinbader opened this issue Jan 24, 2020 · 2 comments · Fixed by #295
Closed

Support for OpenTracing #281

kevinbader opened this issue Jan 24, 2020 · 2 comments · Fixed by #295
Assignees
Milestone

Comments

@kevinbader
Copy link
Contributor

We'd like RIG to be visible to distributed tracing using the OpenTracing API. While it may make sense to communicate some internal events, the first step should be to enable basic tracing of requests through RIG:

  • The reverse proxy should respect tracing headers for incoming HTTP requests and add them to forwarded/outgoing HTTP requests.
  • When producing events, RIG should add tracing info according to the CloudEvents distributed tracing extension spec.
@petermetz
Copy link

Hey,

You might want to look into OpenTelemetry as well/instead. It is positioned as the next iteration of OpenTracing (same team, not a competing standard as far as I understood from their documentation, but don't quote me on that without checking it yourself :-) )

https://opentelemetry.io/

@Knappek
Copy link
Contributor

Knappek commented May 28, 2020

Thank you @petermetz for pointing that out. We have opentelemetry in mind, but I still see a better and easier integration with opencensus. Opentelemetry ensures backwards compatibility with existing opencensus and opentracing though, so it will be an easy switch to opentelemetry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants