[
https://issues.apache.org/jira/browse/CAMEL-26820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26820 started by Claus Ibsen.
-------------------------------------------
> camel-chaos - more to try: a circuit breaker around a route call, the HTTP
> calls of toD, and replay of the files a file route took
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26820
> URL: https://issues.apache.org/jira/browse/CAMEL-26820
> Project: Camel
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Follow-up of CAMEL-26817, from trying the let there be chaos start dialog of
> the Camel TUI on the bundled examples.
> * A circuit breaker around a call to another route of the integration
> ({{direct:supplier}} inside {{circuitBreaker}}) gets no suggestion, so the
> circuit-breaker example has nothing to try. That route stands for the
> service: suggest that it is down for a while ({{outage}}), so the breaker
> opens, and that half of the calls fail ({{rate=0.5}}), past the failure rate
> of the breaker; both expect the caller not to fail, as the fallback answers.
> * The HTTP calls of {{toD}} get no suggestion. Suggest them by the address up
> to the first expression ({{http://localhost:8080/stock/${variable.sku}}} ->
> {{endpoint=http://localhost:8080/stock/*}}), with a 503 (an outage with a
> circuit breaker) and a 404, as a call per resource can find it not there.
> * A file route has no messages to try its rules with, unless someone writes
> files. The files it took are in {{.camel}} (or the folder of its {{move}}
> option): put them back into its folder under their own names (a new chaos
> command {{replay}}), so it takes the same files again. The route moves them
> over the files there, so a replay is the same each time. An experiment puts
> them back while it runs ({{--body=replay:}}), and a route that a file route
> sends to is replayed through it. A route with {{noop=true}} never takes a
> file of the same name again, and one with {{delete=true}} keeps none: no
> replay.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
