[
https://issues.apache.org/jira/browse/CAMEL-26676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139502#comment-18139502
]
Claus Ibsen commented on CAMEL-26676:
-------------------------------------
>From the scripted hands-on run of CAMEL-26675: adding two rules that must both
>be in place before the first fault (an {{at=dlq}} rule and the rule that sends
>an order to the dead letter channel) needs them added in the right order,
>because each {{camel cmd chaos-add}} is a separate CLI run (about a second),
>while an order uses up its redeliveries in 200ms. Suggest {{chaos-add}} (and
>the MCP / camel ask tool) accept more than one rule, added together under one
>lock: {{camel cmd chaos-add myapp --rule=... --rule=...}}.
_Claude Code on behalf of Claus Ibsen_
> camel-chaos - feedback while adding rules: warnings for rules that match
> nothing, skip reasons, lifecycle state and empty output in camel get chaos
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26676
> URL: https://issues.apache.org/jira/browse/CAMEL-26676
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> * {{chaos-add}} / {{chaos-change}} return warnings, shown by the CLI and
> passed through by the MCP tools: the pattern matches no endpoint / step /
> route of the context now (typos such as {{htp://}}, {{step=callStok}}), the
> expectation names a route that does not exist (today a WARN in the
> application log only).
> * Count skips per reason ({{corrupt mode=charset}} on a stream body was
> skipped 79 of 79 with no reason anywhere), in the JSON, the console and the
> CLI.
> * {{camel get chaos}} / {{--report}}: a LIFECYCLE column (down, back in 12s,
> skipped with the reason, left, cancelled), and a line for no rules /
> camel-chaos not on the classpath instead of empty output.
> * {{hooks}} lists the hooks that apply to the matched endpoints, not all the
> hooks of the target (a {{direct:}} rule lists {{poll}}).
> Part of CAMEL-26667 (findings of the hands-on round of camel-chaos stage 1),
> which has the scenarios.
> _Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
