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
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.
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 :-) )
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.
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 text was updated successfully, but these errors were encountered: