[
https://issues.apache.org/jira/browse/CAMEL-26608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26608.
---------------------------------
Resolution: Fixed
Merged to main via https://github.com/apache/camel/pull/29338 (61e20cf392ca).
_Claude Code on behalf of davsclaus_
> camel-jbang - a chaos screen: the rules, the report and the verdict of a
> running integration, live
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26608
> URL: https://issues.apache.org/jira/browse/CAMEL-26608
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Add a chaos screen to the camel-jbang terminal UI (camel-jbang-plugin-tui),
> next to screens like the circuit breaker one, for a running integration that
> has camel-chaos (CAMEL-26330).
> Today the UI only knows whether chaos is on: the AI panel adds a line that
> faults may be injected on purpose ({{TuiToolGroups}}), and {{tui_get_status}}
> has a 'chaos' section. Chaos itself is controlled from {{camel cmd chaos-*}},
> {{camel get chaos}}, the chaos dev console and the MCP tools (CAMEL-26436,
> CAMEL-26454).
> The screen should show:
> * Whether chaos is on or off (on or off is fixed when the integration starts:
> profile {{dev}} or {{camel.chaos.enabled=true}}).
> * The active rules: id, target, fault and parameters, rate, until, and how
> often each one fired; removed rules as in the report.
> * The report per route: completed, failed, failed and kept by the consumer,
> handled by the error handler, redeliveries, faults fired, and skipped faults
> (corrupt on a body it cannot change).
> * Expectations and the verdict: met, unmet (FAIL, with the reason) or pending
> (count so far and time left), and the seed.
> * Live updates while the integration runs.
> Actions, through the CLI connector as {{camel cmd chaos-*}} does: add a rule
> (one-line rule syntax, validated as {{chaos-add}} validates it), change,
> remove and clear. Adding and changing a rule ask for confirmation with the
> rule shown, as for the other actions that change a running integration.
> Out of scope: chaos tools for the AI panel (the design keeps them out on
> purpose); the loose prompts of stage 2 (CAMEL-26607) can be revisited there
> later.
> Add a screenshot of the screen to the docs and to the PR.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
