Updated wrong images
This commit is contained in:
@@ -54,7 +54,7 @@ Subtracting the `cs` timestamp from this timestamp reveals the whole time needed
|
||||
|
||||
The following image shows how *Span* and *Trace* look in a system.
|
||||
|
||||
image::{github-raw}/src/main/asciidoc/images/trace-id.png[Trace Info propagation]
|
||||
image::{github-raw}/docs/src/main/asciidoc/images/trace-id.png[Trace Info propagation]
|
||||
|
||||
Each color of a note signifies a span (there are seven spans - from *A* to *G*).
|
||||
Consider the following note:
|
||||
|
||||
@@ -404,7 +404,7 @@ example. This log configuration was automatically setup by Sleuth. You can disab
|
||||
If you use a log aggregating tool (such as https://www.elastic.co/products/kibana[Kibana], https://www.splunk.com/[Splunk], and others), you can order the events that took place.
|
||||
An example from Kibana would resemble the following image:
|
||||
|
||||
image::{github-raw}/src/main/asciidoc/images/kibana.png[Log correlation with Kibana]
|
||||
image::{github-raw}/docs/src/main/asciidoc/images/kibana.png[Log correlation with Kibana]
|
||||
|
||||
If you want to use https://www.elastic.co/guide/en/logstash/current/index.html[Logstash], the following listing shows the Grok pattern for Logstash:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user