Span initialSpan = this.tracer.nextSpan().name("span").start();
-COUNTRY_CODE.updateValue(initialSpan.context(), "FO");
-bar.updateValue(initialSpan.context(), "2");Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-jdk11-spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Tags.BAGGAGE_FIELD.tag(COUNTRY_CODE, initialSpan);
-Tags.BAGGAGE_FIELD.tag(bar, initialSpan);Tags.BAGGAGE_FIELD.tag(BUSINESS_PROCESS, initialSpan);List of {@link java.util.concurrent.Executor} bean names that should be ignored and not wrapped in a trace representation.
spring.sleuth.baggage-keys
List of baggage key names that should be propagated out of process. These keys will be prefixed with baggage before the actual key. This property is set in order to be backward compatible with previous Sleuth versions. @see brave.propagation.ExtraFieldPropagation.FactoryBuilder#addPrefixedFields(String, java.util.Collection)
spring.sleuth.circuitbreaker.enabled
true
Enable Spring Cloud CircuitBreaker instrumentation.
Span initialSpan = this.tracer.nextSpan().name("span").start();
-COUNTRY_CODE.updateValue(initialSpan.context(), "FO");
-bar.updateValue(initialSpan.context(), "2");Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-jdk11-spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Tags.BAGGAGE_FIELD.tag(COUNTRY_CODE, initialSpan);
-Tags.BAGGAGE_FIELD.tag(bar, initialSpan);Tags.BAGGAGE_FIELD.tag(BUSINESS_PROCESS, initialSpan);With the spring.sleuth.baggage-keys, you set keys that get prefixed with baggage- for HTTP calls and baggage_ for messaging.
-You can also use the spring.sleuth.remote-keys property to pass a list of prefixed keys that are propagated to remote services without any prefix.
-You can also use the spring.sleuth.local-keys property to pass a list keys that will be propagated locally but will not be propagated over the wire.
-Notice that there’s no x- in front of the header keys.
Baggage are fields that are propagated with the trace, optionally out of process. You can use +properties to define fields that have no special configuration such as name mapping:
+spring.sleuth.remote-keys is a list of header names to accept and propagate to remote services.
spring.sleuth.local-keys is a list of names to propagate locally
No prefixing applies with these keys. What you set is literally what is used.
+A name set in either of these properties will result in a BaggageField of the same name.
In order to automatically set the baggage values to Slf4j’s MDC, you have to set @@ -1373,6 +1390,15 @@ Remember that adding entries to MDC can drastically decrease the performance of
If you want to add the baggage entries as tags, to make it possible to search for spans via the baggage entries, you can set the value of
spring.sleuth.propagation.tag.whitelisted-keys with a list of whitelisted baggage keys. To disable the feature you have to pass the spring.sleuth.propagation.tag.enabled=false property.
If you need to do anything more advanced than above, do not define properties and instead use a
+@Bean config for the baggage fields you use.
+ * SingleBaggageField controls header names for one BaggageField.
+ * SingleCorrelationField controls the MDC name of one BaggageField, and whether updates flush.
Span initialSpan = this.tracer.nextSpan().name("span").start();
-COUNTRY_CODE.updateValue(initialSpan.context(), "FO");
-bar.updateValue(initialSpan.context(), "2");Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-jdk11-spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Tags.BAGGAGE_FIELD.tag(COUNTRY_CODE, initialSpan);
-Tags.BAGGAGE_FIELD.tag(bar, initialSpan);Tags.BAGGAGE_FIELD.tag(BUSINESS_PROCESS, initialSpan);Span initialSpan = this.tracer.nextSpan().name("span").start();
-COUNTRY_CODE.updateValue(initialSpan.context(), "FO");
-bar.updateValue(initialSpan.context(), "2");Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-jdk11-spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Unresolved directive in intro.adoc - include::/opt/jenkins/data/workspace/spring-cloud-sleuth-master-ci/spring-cloud-sleuth-core/src/test/resources/application-baggage.yml[indent=0]Tags.BAGGAGE_FIELD.tag(COUNTRY_CODE, initialSpan);
-Tags.BAGGAGE_FIELD.tag(bar, initialSpan);Tags.BAGGAGE_FIELD.tag(BUSINESS_PROCESS, initialSpan);With the spring.sleuth.baggage-keys, you set keys that get prefixed with baggage- for HTTP calls and baggage_ for messaging.
-You can also use the spring.sleuth.remote-keys property to pass a list of prefixed keys that are propagated to remote services without any prefix.
-You can also use the spring.sleuth.local-keys property to pass a list keys that will be propagated locally but will not be propagated over the wire.
-Notice that there’s no x- in front of the header keys.
Baggage are fields that are propagated with the trace, optionally out of process. You can use +properties to define fields that have no special configuration such as name mapping:
+spring.sleuth.remote-keys is a list of header names to accept and propagate to remote services.
spring.sleuth.local-keys is a list of names to propagate locally
No prefixing applies with these keys. What you set is literally what is used.
+A name set in either of these properties will result in a BaggageField of the same name.
In order to automatically set the baggage values to Slf4j’s MDC, you have to set @@ -1373,6 +1390,15 @@ Remember that adding entries to MDC can drastically decrease the performance of
If you want to add the baggage entries as tags, to make it possible to search for spans via the baggage entries, you can set the value of
spring.sleuth.propagation.tag.whitelisted-keys with a list of whitelisted baggage keys. To disable the feature you have to pass the spring.sleuth.propagation.tag.enabled=false property.
If you need to do anything more advanced than above, do not define properties and instead use a
+@Bean config for the baggage fields you use.
+ * SingleBaggageField controls header names for one BaggageField.
+ * SingleCorrelationField controls the MDC name of one BaggageField, and whether updates flush.