Claus Ibsen created CAMEL-26676:
-----------------------------------

             Summary: 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
             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)

Reply via email to