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

Updated docs

Browse Source
This commit is contained in:
Marcin Grzejszczak
2016-11-06 12:31:03 +01:00
parent e5dce64d71
commit 9291af89cf
21 changed files with 38 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -207,41 +207,34 @@ Span ids are extracted from Zipkin-compatible (B3) headers (either `Message`
or HTTP headers), to start or join an existing trace. Trace information is
injected into any outbound requests so the next hop can extract them.
The key change in comparison to the previous versions of Sleuth is that Sleuth is implementing
the Open Tracing's `TextMap` notion. In Sleuth it's called `SpanTextMap`. Basically the idea
is that any means of communication (e.g. message, http request, etc.) can be abstracted via
a `SpanTextMap`. This abstraction defines how one can insert data into the carrier and
how to retrieve it from there. Thanks to this if you want to instrument a new HTTP library
that uses a `FooRequest` as a mean of sending HTTP requests then you have to create an
implementation of a `SpanTextMap` that delegates calls to `FooRequest` in terms of retrieval
and insertion of HTTP headers.
=== Spring Integration
For Spring Integration these are the beans responsible for creation of a Span from a `Message`
and filling in the `MessageBuilder` with tracing information.
For Spring Integration there are 2 interfaces responsible for creation of a Span from a `Message`.
These are:
[source,java]
----
@Bean
public SpanExtractor<Message> messagingSpanExtractor() {
...
}
- `MessagingSpanTextMapExtractor`
- `MessagingSpanTextMapInjector`
@Bean
public SpanInjector<MessageBuilder> messagingSpanInjector() {
...
}
----
You can override them by providing your own implementation and by adding a `@Primary` annotation
to your bean definition.
You can override them by providing your own implementation.
=== HTTP
For HTTP these are the beans responsible for creation of a Span from a `HttpServletRequest`.
For HTTP there are 2 interfaces responsible for creation of a Span from a `Message`.
These are:
[source,java]
----
@Bean
public SpanExtractor<HttpServletRequest> httpServletRequestSpanExtractor() {
...
}
----
- `HttpSpanExtractor`
- `HttpSpanInjector`
You can override them by providing your own implementation and by adding a `@Primary` annotation
to your bean definition.
You can override them by providing your own implementation.
=== Example