SpringCloud/spring-cloud-sleuth
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix incorrect properties used in baggage section (#1662)

Browse Source
This commit is contained in:
Saisurya Kattamuri
2020-06-03 13:36:28 +07:00
committed by GitHub
parent 9feba73fc4
commit 6112b86ab7
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/main/asciidoc/spring-cloud-sleuth.adoc
View File

@@ -90,8 +90,8 @@ Doing so forces the current request to be sampled regardless of configuration.
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-fields` is a list of header names to accept and propagate to remote services.
* `spring.sleuth.local-fields` is a list of names to propagate locally
* `spring.sleuth.baggage.remote-fields` is a list of header names to accept and propagate to remote services.
* `spring.sleuth.baggage.local-fields` is a list of names to propagate locally
No prefixing applies with these keys. What you set is literally what is used.