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

Updating Zipkin settings (#1451)

Browse Source 
Correcting properties name to reflect the code: https://github.com/spring-cloud/spring-cloud-sleuth/blob/master/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/sampler/SamplerProperties.java#L36
This commit is contained in:
Kuba Marchwicki
2019-09-25 14:32:52 +02:00
committed by Marcin Grzejszczak
parent 38ffcbc932
commit fd3deea30e
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/sagan-boot.adoc
View File

@@ -69,6 +69,6 @@ Run this app and then hit the home page. You will see traceId and spanId populat
IMPORTANT: instead of logging the request in the handler explicitly, you could set `logging.level.org.springframework.web.servlet.DispatcherServlet=DEBUG`
IMPORTANT: If you use Zipkin (up till 2.1.x), configure the probability of spans exported by setting `spring.sleuth.sampler.percentage` (default: 0.1, which is 10 percent). Otherwise, you might think that Sleuth is not working because it omits some spans. Starting from 2.2.0, Sleuth will default to rate limited sampler. That means that it will sample up to 1000 transactions per second.
IMPORTANT: If you use Zipkin (up till 2.1.x), configure the probability of spans exported by setting `spring.sleuth.sampler.probability` (default: 0.1, which is 10 percent). Otherwise, you might think that Sleuth is not working because it omits some spans. Starting from 2.2.0, Sleuth will default to rate limited sampler. That means that it will sample up to 1000 transactions per second.
IMPORTANT: Set `spring.application.name=bar` (for instance) to see the service name as well as the trace and span ids.
IMPORTANT: Set `spring.application.name=bar` (for instance) to see the service name as well as the trace and span ids.