Claus Ibsen created CAMEL-26727:
-----------------------------------
Summary: camel-chaos - what to try: chaos rules suggested per
route from what the route does
Key: CAMEL-26727
URL: https://issues.apache.org/jira/browse/CAMEL-26727
Project: Camel
Issue Type: New Feature
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
W-6 of the stage 2 decisions on CAMEL-26607.
>From the routes of the running integration, chaos suggests rules to try, per
>route and ranked, each from a known rule of the chaos model with its targets
>filled in and a line that says why:
* an HTTP call without a circuit breaker: the service answers with an error,
and is slow; with a circuit breaker: the service is down for a while (does it
open, and does the fallback answer);
* a call over another protocol: the connection is refused, and the call is slow;
* an input that can deliver a message again (Kafka, JMS, AMQP, SQS, ...) before
a call out: the call is made twice;
* a dead letter channel: it is unreachable;
* a hand-off over seda/vm/disruptor: the next route fails, with an expectation
that no message is lost between the two routes (CAMEL-26726);
* an event-driven input: the route fails at its entry (what does the sender
see); a polling input: the polls fail; and the route stalls.
camel cmd chaos-suggest [name] prints them with the chaos-add command of each;
the chaos screen of the TUI lists them (w), and Enter types the rule in to add
it.
The hints of the About screen (CAMEL-26716) are meant to be one shared rule
set; these facts come from the running context (chaos only works there), and
can become the chaos part of that set when it is built.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
