From 495bf2cb91ddc3129af2e34093522ebae2eddffd Mon Sep 17 00:00:00 2001 From: Yevgen Polyak Date: Wed, 24 Jul 2024 11:56:02 +1200 Subject: [PATCH] Propagate trace inforation from incoming headers Signed-off-by: Yevgen Polyak --- .../en/operations/observability/tracing/tracing-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/observability/tracing/tracing-overview.md b/daprdocs/content/en/operations/observability/tracing/tracing-overview.md index 603e5d12173..a5194a73086 100644 --- a/daprdocs/content/en/operations/observability/tracing/tracing-overview.md +++ b/daprdocs/content/en/operations/observability/tracing/tracing-overview.md @@ -63,7 +63,7 @@ You must propagate the headers from `service A` to `service B`. For example: `In ##### Pub/sub messages -Dapr generates the trace headers in the published message topic. These trace headers are propagated to any services listening on that topic. +Dapr generates the trace headers in the published message topic. For `rawPayload` messages, it is possible to specify the `traceparent` header to propagate the tracing information. These trace headers are propagated to any services listening on that topic. #### Propagating multiple different service calls