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

Removed mentions of SpanInjector and SpanExtractor

Browse Source
This commit is contained in:
Marcin Grzejszczak
2018-05-16 15:07:57 +02:00
parent 4ff445cf02
commit 03763da653
2 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.adoc
View File

@@ -573,7 +573,6 @@ To that end, Sleuth:
* Sleuth includes default logic to join a trace across HTTP or messaging boundaries.
For example, HTTP propagation works over Zipkin-compatible request headers.
This propagation logic is defined and customized through `SpanInjector` and `SpanExtractor` implementations.
* Sleuth can propagate context (also known as baggage) between processes.
Consequently, if you set a baggage element on a Span, it is sent downstream to other processes over either HTTP or messaging.
@@ -638,7 +637,7 @@ credentials and you already have those.
The projects that require middleware generally include a
`docker-compose.yml`, so consider using
http://compose.docker.io/[Docker Compose] to run the middleware servers
http://compose.docker.io/[Docker Compose] to run the middeware servers
in Docker containers. See the README in the
https://github.com/spring-cloud-samples/scripts[scripts demo
repository] for specific instructions about the common cases of mongo,

1
docs/src/main/asciidoc/features.adoc
View File

@@ -34,7 +34,6 @@ To that end, Sleuth:
* Sleuth includes default logic to join a trace across HTTP or messaging boundaries.
For example, HTTP propagation works over Zipkin-compatible request headers.
This propagation logic is defined and customized through `SpanInjector` and `SpanExtractor` implementations.
* Sleuth can propagate context (also known as baggage) between processes.
Consequently, if you set a baggage element on a Span, it is sent downstream to other processes over either HTTP or messaging.