+
-
+
+
cs timestamp from this timestamp reveals the whole
+
Client Sent event took place.
+
+
+
+
+
Live examples
-
+
Click the Pivotal Web Services icon to see it live!Click the Pivotal Web Services icon to see it live!
@@ -433,12 +433,12 @@ However, if you want to use the legacy Sleuth approaches, you can set the
+
+
+
cs timestamp from this timestamp reveals the whole
+
Client Sent event took place.
+
+
+
+
+
1.2.4. Live examples
-
+
Click the Pivotal Web Services icon to see it live!Click the Pivotal Web Services icon to see it live!
@@ -425,12 +425,12 @@ However, if you want to use the legacy Sleuth approaches, you can set the
+
+
+
Tracer.joinSpan().
TraceContext.Extractor<C> is implemented by a Propagation.Factory plugin.
-Internally, this code creates the union type, TraceContextOrSamplingFlags, with one of the following:
-* TraceContext if trace and span IDs were present.
-* TraceIdContext if a trace ID was present but span IDs were not present.
-* SamplingFlags if no identifiers were present.
TraceContextOrSamplingFlags, with one of the following:
+TraceContext if trace and span IDs were present.
TraceIdContext if a trace ID was present but span IDs were not present.
SamplingFlags if no identifiers were present.
Some Propagation implementations carry extra data from the point of extraction (for example, reading incoming headers) to injection (for example, writing outgoing headers).
For example, it might carry a request ID.
-When implementations have extra data, they handle it as follows:
-* If a TraceContext were extracted, add the extra data as TraceContext.extra().
-* Otherwise, add it as TraceContextOrSamplingFlags.extra(), which Tracer.nextSpan handles.
If a TraceContext were extracted, add the extra data as TraceContext.extra().
Otherwise, add it as TraceContextOrSamplingFlags.extra(), which Tracer.nextSpan handles.
cs timestamp from this timestamp reveals the whole
+
Client Sent event took place.
+
+
+
+
+
Live examples
-
+
Click the Pivotal Web Services icon to see it live!Click the Pivotal Web Services icon to see it live!
@@ -333,12 +333,12 @@ However, if you want to use the legacy Sleuth approaches, you can set the
+
+
+
cs timestamp from this timestamp reveals the whole
+
Client Sent event took place.
+
+
+
+
+
1.2.4. Live examples
-
+
Click the Pivotal Web Services icon to see it live!Click the Pivotal Web Services icon to see it live!
@@ -425,12 +425,12 @@ However, if you want to use the legacy Sleuth approaches, you can set the
+
+
+
Tracer.joinSpan().
TraceContext.Extractor<C> is implemented by a Propagation.Factory plugin.
-Internally, this code creates the union type, TraceContextOrSamplingFlags, with one of the following:
-* TraceContext if trace and span IDs were present.
-* TraceIdContext if a trace ID was present but span IDs were not present.
-* SamplingFlags if no identifiers were present.
TraceContextOrSamplingFlags, with one of the following:
+TraceContext if trace and span IDs were present.
TraceIdContext if a trace ID was present but span IDs were not present.
SamplingFlags if no identifiers were present.
Some Propagation implementations carry extra data from the point of extraction (for example, reading incoming headers) to injection (for example, writing outgoing headers).
For example, it might carry a request ID.
-When implementations have extra data, they handle it as follows:
-* If a TraceContext were extracted, add the extra data as TraceContext.extra().
-* Otherwise, add it as TraceContextOrSamplingFlags.extra(), which Tracer.nextSpan handles.
If a TraceContext were extracted, add the extra data as TraceContext.extra().
Otherwise, add it as TraceContextOrSamplingFlags.extra(), which Tracer.nextSpan handles.