basvanbeek on v0.2.3
basvanbeek on fix-travis
I am also getting a little confused between these two paragraphs in B3 propagation:
If the request already has trace information attached to it, the service should use that information as server receive and server send events are part of the same span as the client send and client receive events If the service calls out to a downstream service a new span is created as a child of the former span. It is identified by the same trace id, a new span id, and the parent id is set to the span id of the previous span. The new span id should be 64 random bits.
My questions is, The B3 propagation document says that, the span ID is same. I'm unable to understand when the span ID should be same and when it should be different.
I currently use the system, where I pass only
trace ID and
span ID as request headers and use the extracted
spanID to generate the
parentID and create a new
spanID, how is this different than B3?
java.lang.NoClassDefFoundError: org/slf4j/MDC at brave.context.slf4j.MDCScopeDecorator.get(MDCScopeDecorator.java:43) at brave.internal.propagation.CorrelationFieldScopeDecorator.decorateScope(CorrelationFieldScopeDecorator.java:36) at brave.propagation.CurrentTraceContext.decorateScope(CurrentTraceContext.java:107) at brave.propagation.ThreadLocalCurrentTraceContext.newScope(ThreadLocalCurrentTraceContext.java:86) at brave.Tracer.withSpanInScope(Tracer.java:441)
Hello, I'm using Istio where the headers are propagated via Sidecar. I have the following scenario:
Service-1 -> (HTTP) -> Service-2 -> (GRPC) -> Service-3
From service 1 to 2 I just propagate the header via http client everything works OK, I was in doubt from service-2 to service-3 where it is GRPC, I already have all the service-2 headers I need to add for service-3 that is grpc, have any examples?
I'm using openzipkin/zipkin:2.21.5 run on okd openshift with some basic default conf (possibly docker run -d -p 9411:9411 openzipkin/zipkin - but I'm not sure, it was installed by admin).
After about one minute I can't go into details of trace from search page to which I could go before moment.
Maybe Zipkin server is running out of memory and deletes old spans - are there any statistics about it?
Maybe it has some default number of detained traces in some circular buffer, if so, how can I increase it?
How can it be checked and configured?
Where can I find any documentation about Zipkin server configuration?
https://hub.docker.com/r/openzipkin/zipkin states mysql is deprecated, elasticsearch link is broken, in-memory is not for prod, where can I find a doc for production configuration?