This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-3.22.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.22.x by this push:
new f76a240501eb Remove xref no longer exists
f76a240501eb is described below
commit f76a240501eb4275cbba0ed54e4e84df58152ce1
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Mar 6 13:18:13 2026 +0100
Remove xref no longer exists
---
components/camel-zipkin/src/main/docs/zipkin.adoc | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/components/camel-zipkin/src/main/docs/zipkin.adoc
b/components/camel-zipkin/src/main/docs/zipkin.adoc
index 56fdc7db9811..2193be3de61a 100644
--- a/components/camel-zipkin/src/main/docs/zipkin.adoc
+++ b/components/camel-zipkin/src/main/docs/zipkin.adoc
@@ -84,17 +84,13 @@ The pattern uses the rules from Intercept.
|includeMessageBody
|false
|Whether to include the Camel message body in the zipkin traces.
-This is not recommended for production usage, or when having big payloads.
-You can limit the size by configuring the
xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
-debug log size].
+This is not recommended for production usage, or when having big payloads.
|includeMessageBodyStreams
|false
|Whether to include message bodies that are stream based in the zipkin traces.
This requires enabling streamcaching on the routes or globally on the
`CamelContext`.
This is not recommended for production usage, or when having big payloads.
-You can limit the size by configuring the
xref:manual:faq:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
-debug log size].
|===
