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

Fixed links to docs

Browse Source
This commit is contained in:
Marcin Grzejszczak
2018-08-31 10:09:37 +02:00
parent 9879c425a6
commit 1036607d87
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.adoc
View File

@@ -492,6 +492,13 @@ dependencies { <2>
If you want to use RabbitMQ or Kafka instead of HTTP, add the `spring-rabbit` or `spring-kafka` dependency.
The default destination name is `zipkin`.
If using Kafka, you must set the property `spring.zipkin.sender.type` property accordingly:
[source,yaml]
----
spring.zipkin.sender.type: kafka
----
CAUTION: `spring-cloud-sleuth-stream` is deprecated and incompatible with these destinations.
If you want Sleuth over RabbitMQ, add the `spring-cloud-starter-zipkin` and `spring-rabbit`
@@ -597,8 +604,8 @@ Consequently, if you set a baggage element on a Span, it is sent downstream to
* If `spring-cloud-sleuth-zipkin` is on the classpath, the app generates and collects Zipkin-compatible traces.
By default, it sends them over HTTP to a Zipkin server on localhost (port 9411).
You can configure the location of the service by setting `spring.zipkin.baseUrl`.
** If you depend on `spring-rabbit` or `spring-kafka`, your app sends traces to a broker instead of HTTP.
**
** If you depend on `spring-rabbit`, your app sends traces to a RabbitMQ broker instead of HTTP.
** If you depend on `spring-kafka`, and set `spring.zipkin.sender.type: kafka`, your app sends traces to a Kafka broker instead of HTTP.
CAUTION: `spring-cloud-sleuth-stream` is deprecated and should no longer be used.