This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch CAMEL-26788-chaos-explore-save
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/CAMEL-26788-chaos-explore-save
by this push:
new e81516c19bf7 CAMEL-26788: docs - where camel cmd chaos-explore saves
the report and the scenarios
e81516c19bf7 is described below
commit e81516c19bf73a7eac712d359ae6e1ea7b26e5cc
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Nov 9 17:41:54 2026 +0100
CAMEL-26788: docs - where camel cmd chaos-explore saves the report and the
scenarios
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
.../src/generated/resources/org/apache/camel/catalog/docs/chaos.adoc | 3 ++-
components/camel-chaos/src/main/docs/chaos.adoc | 3 ++-
docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc | 5 ++++-
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/chaos.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/chaos.adoc
index e483e2919166..845687a8b8d4 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/chaos.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/chaos.adoc
@@ -424,7 +424,8 @@ The Camel CLI runs an experiment in one call: `camel cmd
chaos-experiment` begin
`--body`, `--repeat` and `--interval`, as `camel cmd send`), waits until its
expectations are decided (at most
`--wait`), and ends it. `camel cmd chaos-explore-start` and
`chaos-explore-finish` start and finish the exploration.
`camel cmd chaos-explore` hands a whole exploration to an AI: it runs the
experiments by itself for the budget, and
-reports what held and what broke (the MCP prompt `camel_chaos_explore` is the
same playbook).
+reports what held and what broke (the MCP prompt `camel_chaos_explore` is the
same playbook). It saves the report in
+`test/chaos/reports`, and each experiment that failed as a scenario in
`test/chaos`, to replay it.
== Scenarios
diff --git a/components/camel-chaos/src/main/docs/chaos.adoc
b/components/camel-chaos/src/main/docs/chaos.adoc
index e483e2919166..845687a8b8d4 100644
--- a/components/camel-chaos/src/main/docs/chaos.adoc
+++ b/components/camel-chaos/src/main/docs/chaos.adoc
@@ -424,7 +424,8 @@ The Camel CLI runs an experiment in one call: `camel cmd
chaos-experiment` begin
`--body`, `--repeat` and `--interval`, as `camel cmd send`), waits until its
expectations are decided (at most
`--wait`), and ends it. `camel cmd chaos-explore-start` and
`chaos-explore-finish` start and finish the exploration.
`camel cmd chaos-explore` hands a whole exploration to an AI: it runs the
experiments by itself for the budget, and
-reports what held and what broke (the MCP prompt `camel_chaos_explore` is the
same playbook).
+reports what held and what broke (the MCP prompt `camel_chaos_explore` is the
same playbook). It saves the report in
+`test/chaos/reports`, and each experiment that failed as a scenario in
`test/chaos`, to replay it.
== Scenarios
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 4720ad63b47e..e744bbfe3775 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc
@@ -954,7 +954,10 @@ camel cmd chaos-explore --budget=10m
camel cmd chaos-explore myApp --budget=1h --focus=refunds --api-type=anthropic
----
-Run the integration with `--stub=remote`, so the experiments do not reach real
systems. A route fed over HTTP or from
+It saves what it found in the project: the report and the journal in
`test/chaos/reports/explore-<time>.md` (and
+`.json`), and each experiment that failed as a scenario,
`test/chaos/explore-<time>-<n>.chaos`, which
+`camel run * --chaos=<file>` or `camel cmd chaos-load` replays (`--no-save`
leaves them out). Run the integration with
+`--stub=remote`, so the experiments do not reach real systems. A route fed
over HTTP or from
files cannot be fed by an experiment yet. MCP clients have the same playbook
as the prompt `camel_chaos_explore`. See
xref:next@components:others:chaos.adoc#_an_exploration[An exploration] in the
camel-chaos documentation.
