From 66e5a8f5b601e3e7f2d65553dfe713463cabe407 Mon Sep 17 00:00:00 2001 From: Dmitry Aleksandrov Date: Mon, 13 Nov 2023 11:26:51 +0200 Subject: [PATCH] Minor fixes Signed-off-by: Dmitry Aleksandrov --- docs/se/guides/tracing.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/se/guides/tracing.adoc b/docs/se/guides/tracing.adoc index 5faa24a9c54..34d2e542bc6 100644 --- a/docs/se/guides/tracing.adoc +++ b/docs/se/guides/tracing.adoc @@ -253,7 +253,7 @@ image::guides/12_tracing_span_detail.png[Span Details] Helidon automatically traces across services if the services use the same tracer, for example, the same instance of Jaeger. This means a single trace can include spans from multiple services and hosts. Helidon uses a `SpanContext` to propagate tracing information across process boundaries. When you make client API calls, Helidon will -internally call OpenTelemetry APIs or OpenTracing APIs to propagate the Span Context. There is nothing you need to do in your application to make this work. +internally call OpenTelemetry APIs or OpenTracing APIs to propagate the `SpanContext`. There is nothing you need to do in your application to make this work. To demonstrate distributed tracing, you will need to create a second project, where the server listens to on port 8081. Create a new root directory to hold this new project, then do the following steps, similar to @@ -295,7 +295,7 @@ cd helidon-quickstart-se-2 helidon-tracing-providers-jaeger <3> ---- -<1> Helidon Tracing API dependencies. +<1> Helidon Tracing API. <2> Observability features for tracing. <3> Jaeger tracing provider. @@ -477,6 +477,7 @@ public class GreetService implements HttpService { String result = requestBuilder // <4> .get(String.class); response.send(result); + spa.end(); } catch (Throwandle t) { span.end(t); // <5> }