This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch feature/CAMEL-23722-cli-docs-restructure in repository https://gitbox.apache.org/repos/asf/camel.git
commit 05910b402b9b0bfa3ae1be97ddd8c6719d65312f Author: Claus Ibsen <[email protected]> AuthorDate: Tue Jun 9 20:37:42 2026 +0200 CAMEL-23722: Add TUI cross-references to Getting Started, Managing, and Debugging Co-Authored-By: Claude Opus 4.6 <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc | 3 +++ docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc | 4 ++++ docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc | 4 ++++ 3 files changed, 11 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc index eb07bef9a4f9..1dea78edf732 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc @@ -2,6 +2,9 @@ The Camel CLI provides built-in debugging capabilities — from Camel's own route debugger to standard Java debugging. For the full overview, see xref:camel-jbang.adoc[Camel CLI]. +TIP: The xref:camel-jbang-tui.adoc[Camel TUI] includes a Spans tab that shows OpenTelemetry traces +as a waterfall view — useful for understanding message flow and spotting slow processors. + == Camel route debugging *Available since Camel 4.2* diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc index 57d780a2f1af..166d11bed95b 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc @@ -83,6 +83,10 @@ This works for all DSLs (YAML, Java, XML). TIP: Dev mode is the fastest way to prototype integrations. Keep it running while you iterate on your routes. +TIP: Want a visual overview of your running routes, message flow, and health status — right in the terminal? +Try the xref:camel-jbang-tui.adoc[Camel TUI] (`camel tui`), a full-featured dashboard that works +over SSH, in containers, and anywhere a browser is not available. + == Try a built-in example Don't have a route yet? The CLI ships with a catalog of ready-to-run examples: diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc index 803c2697348f..b972290eae41 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc @@ -2,6 +2,10 @@ Once your Camel integrations are running, the CLI provides comprehensive management and monitoring capabilities — from listing processes and tailing logs to tracing messages and checking health. +TIP: Prefer a visual dashboard over individual commands? +The xref:camel-jbang-tui.adoc[Camel TUI] (`camel tui`) shows routes, messages, health, traces, +and more in a single terminal view — everything on this page, at a glance. + == Controlling local Camel integrations List running integrations with `ps`:
