A place to document (and discuss) the OpenTracing specification. 🛑 This project is DEPRECATED! https://github.com/opentracing/specification/issues/163
General question to see what the feeling is regarding capturing information in the trace data about such situations in a standard way (tags/references).
As mentioned by @adriancole in https://github.com/opentracing-contrib/java-apache-httpclient/pull/2#discussion_r114044848, where the redirection is currently recorded in log data, it would be good practice for any distinct communication to be represented in a separate span - although I don't think this is stated in the spec anywhere - should this be added as a guideline, or a requirement?
Taking into account fallbacks aswell, it may be good to highlight that a redirection or fallback is related to a previous SpanContext (i.e. via reference) to facilitate later understanding of what actually occurred at runtime.
Similarly with circuit breaker pattern - I think it might be good to have the fact that it occurred recorded in some standard way.
MahatmaFatalError
commented
5 years ago
General question to see what the feeling is regarding capturing information in the trace data about such situations in a standard way (tags/references).
As mentioned by @adriancole in https://github.com/opentracing-contrib/java-apache-httpclient/pull/2#discussion_r114044848, where the redirection is currently recorded in log data, it would be good practice for any distinct communication to be represented in a separate span - although I don't think this is stated in the spec anywhere - should this be added as a guideline, or a requirement?
Taking into account fallbacks aswell, it may be good to highlight that a redirection or fallback is related to a previous
SpanContext(i.e. via reference) to facilitate later understanding of what actually occurred at runtime.Similarly with circuit breaker pattern - I think it might be good to have the fact that it occurred recorded in some standard way.