[
https://issues.apache.org/jira/browse/CAMEL-26678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26678 started by Claus Ibsen.
-------------------------------------------
> camel-chaos - live state of the rules: observed rate, recent faults, the
> effect of each rule, and the exchange marked with the rule
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26678
> URL: https://issues.apache.org/jira/browse/CAMEL-26678
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The data for the chaos screen (CAMEL-26608), also in the console, the JSON
> report, {{camel get chaos}} and the MCP tools:
> * per rule: the observed rate next to the target ({{5.1% of 5%}}), when it
> last fired, the next match of an {{every:N}} rule, faults per second over the
> last minute;
> * a small ring buffer of the last faults: time, exchange id, route, endpoint
> or step, fault;
> * a faulted exchange gets the exchange property {{CamelChaosRule}} (a
> property, not a header), so the tracer, the message history and a DLQ route
> show it;
> * the effect of a rule: of the exchanges it faulted, how many were recovered
> by redelivery, handled by the error handler, failed, still in flight (a 3s
> stop of a route sent 5 orders to the DLQ because 2 x 100ms redelivery is too
> short; today nothing ties the two).
> 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)
