Updated docs
This commit is contained in:
@@ -380,3 +380,13 @@ and then just annotate your main class with `@EnableZipkinStreamServer` annotati
|
||||
----
|
||||
include::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin-stream/src/main/java/example/ZipkinStreamServerApplication.java[]
|
||||
----
|
||||
|
||||
== Additional resources
|
||||
|
||||
*Adrian Cole giving an introduction to ditributed tracing with Zipkin*
|
||||
|
||||
video::f9J1Av8rwCE[youtube]
|
||||
|
||||
*Marcin Grzejszczak talking about Spring Cloud Sleuth and Zipkin*
|
||||
|
||||
video::eQV71Mw1u1c[youtube]
|
||||
@@ -520,7 +520,7 @@ the same as the ones sent in HTTP (they contain a `-`) in its name. For the sake
|
||||
backwards compatibility in 1.0.4 we've started sending both valid and invalid headers. Please upgrade to 1.0.4 because
|
||||
in Spring Cloud Sleuth 1.1 we will remove the support for the deprecated headers.
|
||||
|
||||
Since 1.0.4 you can provide the `spring.sleuth.integration.patterns` pattern to explicitly
|
||||
You can provide the `spring.sleuth.integration.patterns` pattern to explicitly
|
||||
provide the names of channels that you want to include for tracing. By default all channels
|
||||
are included.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user