This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 21e0253961d CAMEL-19033: camel-jbang - get trace -> trace
21e0253961d is described below
commit 21e0253961da237b915cb927619a4f02adcb0008
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Feb 15 19:34:49 2023 +0100
CAMEL-19033: camel-jbang - get trace -> trace
---
.../modules/ROOT/pages/camel-jbang.adoc | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
index 06f4eb6adb0..b9638247436 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
@@ -836,6 +836,28 @@ camel log chuck --grep=error --follow=false
This will grep the logs for log lines with matches text `error` and output
only these logs, and exit.
+==== Tracing messages
+
+The `trace` command is used for showing how messages are routed in Camel. The
command has similar output as the `log`
+command but only display message tracing information. This allows you to see
every _step_ a message is routed in Camel.
+
+The `trace` command has many options and can be used to _filter_, _grep_ or
output on different detail _levels`.
+The _exchange id_ is logged (and grouped by colour), so you can use that to
correlate the events, when traces are interleaved.
+
+For example if an existing integration is running named chuck, you can trace
it as follows:
+
+[source,bash]
+----
+camel trace chuck
+----
+
+You can also trace all running integrations
+
+[source,bash]
+----
+camel trace
+----
+
==== Running Camel integrations in background
The `run` command allows to run Camel in the background with the
`--background` option.
