a SpanCollector
a List of span filters for client spans. List can be empty if you don't want trace filtering (sampling). The trace filters will be executed in order. If one returns false there will not be tracing and the next trace filters will not be executed anymore.
In a typical server-side app, it might be a good idea to have a { s => s.isSetParent_id } in here
in case you want to make sure no orphaned client-spans get sent.
*Note* this will only be used for clientReceived, not clientSent.
List of span filters for client spans. List can be empty if you don't want trace filtering (sampling). The trace filters will be executed in order. If one returns false there will not be tracing and the next trace filters will not be executed anymore.
*Note* this will only be used for serverReceived, not serverSent.
Customisable client span type
Customisable client span type
Customisable server span type
Customisable server span type
Creates a ClientSpan with a ClientReceived annotation that will be used to signal to the Zipkin collector that a Client Received event has occurred at the current time.
Creates a ClientSpan with a ClientReceived annotation that will be used to signal to the Zipkin collector that a Client Received event has occurred at the current time.This method *should* be used to also actually send the underlying Span to the Zipkin server.
If annotations are provided, they will also be added.
Creates a ClientSpan with a ClientSent annotation that will later be used to signal to the Zipkin collector that a Client Sent event has occurred at the current time.
Creates a ClientSpan with a ClientSent annotation that will later be used to signal to the Zipkin collector that a Client Sent event has occurred at the current time.
If annotations are provided, they will also be added.
Provides a way of turning a custom ClientSpan back into a normal Span
Provides a way of turning a custom ClientSpan back into a normal Span
The execution context provided by and used within this service for tracing purposes
The execution context provided by and used within this service for tracing purposes
Returns a Span based on a name and a parent Span, which may or may not be used
Returns a Span based on a name and a parent Span, which may or may not be used
In essence, checks for a trace id on the parent Span, if it exists, uses the parent Span's trace id as the returned Span's trace id and the parent id as the returned Span's parentId.
The returned Span is guaranteed to have a new id and the name passed.
Returns an id
Returns an id
Determines if the Span is minimally sendable to Zipkin (has an id, has a trace id, and has a non-empty name)
Determines if the Span is minimally sendable to Zipkin (has an id, has a trace id, and has a non-empty name)
Returns a ServerSpan with a ServerReceived annotation that will later be used to signal to the Zipkin collector that a server received event has occurred at the current time.
Returns a ServerSpan with a ServerReceived annotation that will later be used to signal to the Zipkin collector that a server received event has occurred at the current time.
If annotations are provided, they will also be added.
Returns a ServerSpan with a ServerSent annotation that will be used to signal to the Zipkin collector that a server Sent event has occurred at the current time.
Returns a ServerSpan with a ServerSent annotation that will be used to signal to the Zipkin collector that a server Sent event has occurred at the current time. This method *should* be used to also actually send the underlying Span to the Zipkin server.
If annotations are provided, they will also be added.
Provides a way of turning a custom ServerSpan back into a normal Span
Provides a way of turning a custom ServerSpan back into a normal Span
Turns a Span into a Map[String, String].
Turns a Span into a Map[String, String].
The keys of the map are the official Zipkin id Header strings (e.g. X-B3-TraceId), and the values are the hexadecimal string versions of those ids.
Useful turning a Span into a data structure that can be more easily serialised in order to be passed onto other systems via some kind of transport protocol.
ZipkinService based on Brave.
There should be at most 1 of these instances in a given running app, shared between multiple objects that need tracing.