[
https://issues.apache.org/jira/browse/CAMEL-26774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26774 started by Claus Ibsen.
-------------------------------------------
> camel-chaos - the experiments of an exploration: what each one did, and its
> verdict, in the journal
> ---------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26774
> URL: https://issues.apache.org/jira/browse/CAMEL-26774
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Step 5 of CAMEL-26760 ("let there be chaos"), part 1: the experiments of an
> exploration (CAMEL-26773) in its journal.
> * {{ChaosManager.beginExperiment(hypothesis, rules)}}: while an exploration
> runs, one experiment at a time. It adds its rules (all or none, as
> {{addRules}}) and takes a snapshot of the counts per route.
> * {{endExperiment(note)}}: what the experiment did, recorded in the journal:
> per route the exchanges completed, failed (kept by the consumer), handled and
> redelivered since it began, the faults of its rules, the outcome of their
> expectations, and a verdict (FAIL with an unmet expectation, PENDING with one
> not decided yet, else PASS). Its rules are removed.
> * An experiment that is still open at the deadline is ended then.
> * The report has the experiments of the exploration, and the one open now
> with the state of its expectations, so a tool can wait until they are decided.
> * The chaos action of the CLI connector: {{experiment-begin}} and
> {{experiment-end}}.
> Part 2 (after CAMEL-26767 and this): one experiment per call, with its
> traffic ({{camel cmd send --repeat}}) and the wait for its expectations, as
> {{camel cmd chaos-experiment}} and the AI and MCP tools.
> _Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
