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 d4cdfd657633 CAMEL-25426: docs - screenshots for the monitor pages, 
and its actions menu as it is now (#27517)
d4cdfd657633 is described below

commit d4cdfd65763367a43fabd8d0bf4e24f426cc8499
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Oct 8 07:25:44 2026 +0200

    CAMEL-25426: docs - screenshots for the monitor pages, and its actions menu 
as it is now (#27517)
    
    Screenshots where the monitor pages had none: the example browser, the
    actions menu, the Activity tab, the Architecture view, the Ollama tab, the
    Memory Leak tab and SQL Query.
    
    The actions menu table listed "Run from folder...", which the menu no longer
    has, and left out Go to (Shift+F2), Switch Integration (F3), Screen..., AI &
    MCP... and Shell. The Doctor list left out the Ollama, AI and MCP checks.
    
    
    Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
    
    Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
---
 .../ROOT/images/jbang/camel-tui-actions-menu.png      | Bin 0 -> 381942 bytes
 .../images/jbang/camel-tui-diagram-architecture.png   | Bin 0 -> 439561 bytes
 .../ROOT/images/jbang/camel-tui-example-browser.png   | Bin 0 -> 416706 bytes
 .../ROOT/images/jbang/camel-tui-observe-activity.png  | Bin 0 -> 580910 bytes
 .../images/jbang/camel-tui-observe-memory-leak.png    | Bin 0 -> 437003 bytes
 .../ROOT/images/jbang/camel-tui-observe-sql-query.png | Bin 0 -> 191815 bytes
 .../ROOT/images/jbang/camel-tui-ollama-tab.png        | Bin 0 -> 355399 bytes
 .../modules/ROOT/pages/camel-jbang-tui-diagram.adoc   |   2 ++
 .../ROOT/pages/camel-jbang-tui-getting-started.adoc   |   2 ++
 .../ROOT/pages/camel-jbang-tui-local-models.adoc      |   2 ++
 .../modules/ROOT/pages/camel-jbang-tui-observe.adoc   |   6 ++++++
 .../modules/ROOT/pages/camel-jbang-tui-settings.adoc  |  18 ++++++++++++------
 12 files changed, 24 insertions(+), 6 deletions(-)

diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-actions-menu.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-actions-menu.png
new file mode 100644
index 000000000000..3a95187e2f63
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-actions-menu.png differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-diagram-architecture.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-diagram-architecture.png
new file mode 100644
index 000000000000..b0fb362321c2
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-diagram-architecture.png 
differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-example-browser.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-example-browser.png
new file mode 100644
index 000000000000..9ea0a42039ab
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-example-browser.png 
differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-activity.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-activity.png
new file mode 100644
index 000000000000..61dc97bd035d
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-activity.png 
differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-memory-leak.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-memory-leak.png
new file mode 100644
index 000000000000..b299f55d54df
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-memory-leak.png 
differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-sql-query.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-sql-query.png
new file mode 100644
index 000000000000..f42050510001
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-observe-sql-query.png 
differ
diff --git 
a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ollama-tab.png 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ollama-tab.png
new file mode 100644
index 000000000000..b8c5ac62e0f6
Binary files /dev/null and 
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ollama-tab.png differ
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-diagram.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-diagram.adoc
index d624c89f6c7f..a981a3ea065d 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-diagram.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-diagram.adoc
@@ -95,6 +95,8 @@ routes grouped by what they do for the business, one box per 
group, so a project
 reads as a handful of boxes. The view reads the source files of the selected 
integration, not the
 running routes.
 
+image::jbang/camel-tui-diagram-architecture.png[The Architecture level after 
the AI overview: four capabilities of an order flow and how they talk]
+
 Each route has one role:
 
 * *route group* -- the routes that set `group` in the source. The source 
always wins, and these
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-getting-started.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-getting-started.adoc
index f7f854f0f5e9..e331ceca0ded 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-getting-started.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-getting-started.adoc
@@ -38,6 +38,8 @@ camel tui
 . Browse the example catalog -- type to filter by name
 . Press *Enter* to launch the selected example
 
+image::jbang/camel-tui-example-browser.png[The Quick start group of the 
example browser, with the legend of the icons]
+
 Before launching, a run options form lets you choose the *runtime*: Camel Main 
(standalone),
 Spring Boot, Quarkus, or JBang. This makes it easy to try any example on all 
three runtimes without
 changing a single line of code. The first three run the example in a separate 
JVM that only
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-local-models.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-local-models.adoc
index 1f742482cb0d..31aa7eef809a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-local-models.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-local-models.adoc
@@ -168,6 +168,8 @@ running integration: it finds Ollama at `localhost:11434`, 
at the address of `ca
 or at the endpoint the AI panel (*F8*) is using. The tab is listed only while 
an Ollama server answers;
 the TUI checks every ten seconds, so it appears shortly after `ollama serve` 
starts.
 
+image::jbang/camel-tui-ollama-tab.png[The Ollama tab with qwen3.6 loaded: 
throughput, context, host and the last question]
+
 * *Model* -- the loaded model with its family, parameters, quantization, 
layers, experts (and how many
   are active per token for a mixture-of-experts model), how much of it sits in 
GPU memory, the
   allocated context length and when Ollama will unload it. With no model 
loaded, the installed models
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-observe.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-observe.adoc
index 37e82de2cfa0..f3886441cd73 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-observe.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-observe.adoc
@@ -29,6 +29,8 @@ dev mode or explicit enablement, the tab is empty.
 The top panel shows aggregated statistics: total / OK / failed exchange 
counts, total sends,
 p50 / p95 / max elapsed times, and the time window of the visible entries.
 
+image::jbang/camel-tui-observe-activity.png[The Activity tab: the last 
exchanges of three Kafka routes and a file route, with the summary on top]
+
 Select an exchange to see its details below: exchange ID, route, elapsed time, 
the remote endpoints
 called during the exchange with individual timings, and exception details if 
the exchange failed.
 
@@ -264,6 +266,8 @@ When your integration includes a DataSource, two SQL tabs 
appear under More > Da
 * *SQL Trace* -- captures and displays SQL statements executed by your routes 
in real-time,
   showing query text, execution time, and the route that triggered them.
 
+image::jbang/camel-tui-observe-sql-query.png[A query in the SQL Query tab 
against the DataSource of the integration, with the key column marked]
+
 === Memory Leak Detection
 
 The Memory Leak tab (under More > JVM) uses Java Flight Recorder (JFR) to 
diagnose memory leaks
@@ -271,6 +275,8 @@ in your running integration. It runs two sequential 
recordings and compares obje
 classifying each class as growing, stable, shrinking, new, or gone. This is 
lightweight and safe
 for production use.
 
+image::jbang/camel-tui-observe-memory-leak.png[Two recordings compared: byte 
arrays grow 133% and are flagged as a leak, with the line of code that 
allocates them]
+
 === JFR Runtime Profiling
 
 The JFR tab (under More > Observability) gives you a lightweight profiling 
view of your running integration
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-settings.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-settings.adoc
index d786640d8fc8..d81a407428d7 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-settings.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-settings.adoc
@@ -23,21 +23,25 @@ Press *F2* to open the actions menu with quick access to 
common operations:
 |===
 | Action | Description
 
+| Go to... (Shift+F2) | Jump to a tab by name.
+| Switch Integration (F3) | Select another running integration.
 | Send Message | Send a test message to any route with custom body, headers, 
and exchange pattern.
-| Run an example... | Browse and launch built-in Camel examples from the 
catalog.
+| Run an Example... | Browse and launch built-in Camel examples from the 
catalog.
 | Open Project... | Open a project directory in the Source tab for browsing 
and editing. Run with F10.
-| Run from folder... | Run routes from a local directory.
 | Run Dev/Infra Service... | Start infrastructure services (Kafka, databases, 
etc.) in Docker.
-| Browse Files | Browse the integration's source files with syntax 
highlighting.
-| Run Doctor | Check your environment: Java version, JBang, Maven, Docker, 
port conflicts, disk space.
+| Browse Files... | Browse the integration's source files with syntax 
highlighting.
+| Run Doctor | Check your environment: Java, JBang, Maven, Docker, Ollama, AI 
and MCP, port conflicts, disk space.
 | Reset Stats | Reset all statistics and metrics for the selected integration.
 | Stop All | Stop running integrations and/or infrastructure services.
+| Screen... | Take a screenshot (SVG, text, or ANSI art), record the session 
as a `.tape` file, show keystrokes, or add a caption, for demos.
 | Settings... | Change the theme, the starting tab, and the default 
run-from-folder.
-| Take Screenshot | Export the current screen as SVG, text, or ANSI art.
-| Start/Stop Tape Recording | Record your session as a `.tape` file for demos.
+| AI & MCP... | AI Prompt, Setup AI and AI Log (see 
xref:camel-jbang-tui-ai.adoc[AI]), and MCP Info and MCP Log: the MCP server of 
the session and the calls agents made to it. Called AI... when the MCP server 
is off.
+| Shell (F6) | Open the embedded Camel CLI shell.
 | Quit | Quit the TUI, with the same confirmation as pressing *q*. The last 
entry of the menu, so quitting is one menu away on tabs and in input fields 
where *q* is taken by something else. Integrations started from the TUI keep 
running after it quits (until the terminal closes); when some do, the 
confirmation says how many, and *s* stops them and quits.
 |===
 
+image::jbang/camel-tui-actions-menu.png[The F2 actions menu over the Overview]
+
 === Sending Test Messages
 
 Select *Send Message* from the F2 menu (or press *F2* then choose it):
@@ -62,6 +66,8 @@ The Doctor checks your development environment and reports 
issues:
 * JBang installation
 * Maven repository connectivity
 * Docker/Podman availability
+* Ollama: whether it runs, and the models it has (the AI panel needs one of 
14B or more)
+* AI and MCP: the AI provider and model set up, and the MCP server of the 
session
 * Common port conflicts (8080, 8443, 9090)
 * Disk space in temp directory
 

Reply via email to