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-jbang-examples.git


The following commit(s) were added to refs/heads/main by this push:
     new 19f6a48  Keep showcase/smart-log-analyzer out of the example catalog 
(#102)
19f6a48 is described below

commit 19f6a48b46934901774ede83705d2321308e344f
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Oct 8 07:41:10 2026 +0200

    Keep showcase/smart-log-analyzer out of the example catalog (#102)
    
    It is several apps, run one by one as its README says, so camel run
    --example and the example browsers, which run an example as one
    integration, cannot start it. It is marked "exclude": true, as the other
    larger reference examples are: it stays in the repository with its README,
    but leaves the catalog and the example tables. Closes #98.
    
    
    Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
    
    Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
---
 AGENTS.md                                 |  5 +--
 README.md                                 |  1 -
 camel-jbang-example-catalog.json          | 59 -------------------------------
 showcase/README.md                        |  1 -
 showcase/smart-log-analyzer/metadata.json |  3 +-
 5 files changed, 5 insertions(+), 64 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 38aae00..dfaa2a8 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -53,8 +53,9 @@ group order and intros.
   `camel-jbang-example-catalog.json` and the example tables in the root and 
group
   READMEs. Do not hand-edit the catalog or those tables; run
   `./generate-catalog.sh` after adding or changing a `metadata.json`.
-- `security/`, `transformation/` and the non-ladder examples in `cloud/` are
-  larger reference examples marked `"exclude": true`; they are not on the 
ladder.
+- `security/`, `transformation/`, the non-ladder examples in `cloud/` and
+  `showcase/smart-log-analyzer` (several apps, run one by one as its README 
says)
+  are larger reference examples marked `"exclude": true`; they are not on the 
ladder.
 
 ## Anatomy of an example
 
diff --git a/README.md b/README.md
index 8d14c84..07cbbbb 100644
--- a/README.md
+++ b/README.md
@@ -144,7 +144,6 @@ Tooling demos outside the ladder: the TUI, a memory leak, 
message sizes, log ana
 | [TUI Hello World](showcase/tui-hello-world/) | A one-shot timer prints an 
invitation; the route direct:greet then logs and greets any message sent to it 
from the CLI (camel cmd send --endpoint=direct:greet --body=...) or from a tool 
that can send messages. | nothing |
 | [Memory Leak](showcase/memory-leak/) | Three timer routes run side by side: 
two leak memory into a cache and a buffer, one is healthy, so a JFR Old Object 
Sample recording and the CLI's heap tools show which route leaks. | nothing |
 | [Message Size](showcase/message-size/) | Timer routes send messages of 
small, medium and large sizes to seda queues with a Content-Length header, so 
camel cmd and the CLI's message-size views show sizes per endpoint. | nothing |
-| [Smart Log Analyzer](showcase/smart-log-analyzer/) | A multi-part showcase: 
a load generator produces logs and traces, a correlator maps OpenTelemetry logs 
to traces, an LLM analyses the correlated records, and a small web console with 
a REST API shows the results. | nothing |
 <!-- examples:end -->
 
 The directories `security`, `transformation` and the rest of `cloud` hold 
larger examples outside the ladder,
diff --git a/camel-jbang-example-catalog.json b/camel-jbang-example-catalog.json
index ee1623b..4c5c027 100644
--- a/camel-jbang-example-catalog.json
+++ b/camel-jbang-example-catalog.json
@@ -1293,65 +1293,6 @@
         ],
         "order": 3
     },
-    {
-        "name": "showcase/smart-log-analyzer",
-        "title": "Smart Log Analyzer",
-        "description": "A multi-part showcase: a load generator produces logs 
and traces, a correlator maps OpenTelemetry logs to traces, an LLM analyses the 
correlated records, and a small web console with a REST API shows the results.",
-        "level": "showcase",
-        "teaches": {
-            "components": [
-                "platform-http",
-                "jms",
-                "file",
-                "langchain4j-chat"
-            ],
-            "eips": [
-                "rest"
-            ]
-        },
-        "tags": [
-            "ai",
-            "observability",
-            "opentelemetry",
-            "logging"
-        ],
-        "bundled": false,
-        "requiresDocker": false,
-        "hasCitrusTests": true,
-        "files": [
-            "README.md",
-            "analyzer/application-dev.properties",
-            "analyzer/error-analyzer.camel.yaml",
-            "containers/caches/infinispan-events-config.json",
-            "containers/caches/infinispan-events-to-process-config.json",
-            "containers/otel-collector-config.yaml",
-            "correlator/application-dev.properties",
-            "correlator/correlated-log-schema.json",
-            "correlator/correlated-trace-schema.json",
-            "correlator/infinispan.camel.yaml",
-            "correlator/kafka-ca-cert.pem",
-            "correlator/kaoto-datamapper-4a94acc3.xsl",
-            "correlator/kaoto-datamapper-8f5bb2dd.xsl",
-            "correlator/logs-mapper.camel.yaml",
-            "correlator/otel-log-record-schema.json",
-            "correlator/otel-logs-schema.json",
-            "correlator/otel-span-schema.json",
-            "correlator/otel-traces-schema.json",
-            "correlator/traces-mapper.camel.yaml",
-            "first-iteration/analyzer.camel.yaml",
-            "first-iteration/application.properties",
-            "first-iteration/load-generator.camel.yaml",
-            "log-generator/agent.properties",
-            "log-generator/application-dev.properties",
-            "log-generator/log-generator.camel.yaml",
-            "log-generator/opentelemetry-javaagent.jar",
-            "ui-console/application-dev.properties",
-            "ui-console/index.html",
-            "ui-console/jms-file-storage.camel.yaml",
-            "ui-console/rest-api.camel.yaml"
-        ],
-        "order": 4
-    },
     {
         "name": "showcase/tui-hello-world",
         "title": "TUI Hello World",
diff --git a/showcase/README.md b/showcase/README.md
index 9bc3925..dc6ea1e 100644
--- a/showcase/README.md
+++ b/showcase/README.md
@@ -8,7 +8,6 @@ Tooling demos outside the ladder: the TUI, a memory leak, 
message sizes, log ana
 | [TUI Hello World](tui-hello-world/) | A one-shot timer prints an invitation; 
the route direct:greet then logs and greets any message sent to it from the CLI 
(camel cmd send --endpoint=direct:greet --body=...) or from a tool that can 
send messages. | nothing |
 | [Memory Leak](memory-leak/) | Three timer routes run side by side: two leak 
memory into a cache and a buffer, one is healthy, so a JFR Old Object Sample 
recording and the CLI's heap tools show which route leaks. | nothing |
 | [Message Size](message-size/) | Timer routes send messages of small, medium 
and large sizes to seda queues with a Content-Length header, so camel cmd and 
the CLI's message-size views show sizes per endpoint. | nothing |
-| [Smart Log Analyzer](smart-log-analyzer/) | A multi-part showcase: a load 
generator produces logs and traces, a correlator maps OpenTelemetry logs to 
traces, an LLM analyses the correlated records, and a small web console with a 
REST API shows the results. | nothing |
 
 Start with [TUI Hello World](tui-hello-world/); the others stand on their own, 
in any order.
 
diff --git a/showcase/smart-log-analyzer/metadata.json 
b/showcase/smart-log-analyzer/metadata.json
index b1d97d1..b099ed4 100644
--- a/showcase/smart-log-analyzer/metadata.json
+++ b/showcase/smart-log-analyzer/metadata.json
@@ -20,5 +20,6 @@
         "opentelemetry",
         "logging"
     ],
-    "bundled": false
+    "bundled": false,
+    "exclude": true
 }

Reply via email to