Claus Ibsen created CAMEL-26698:
-----------------------------------
Summary: camel-console - the redeliveries and the failures handled
of routes and processors, and show them in the camel-jbang Routes tab
Key: CAMEL-26698
URL: https://issues.apache.org/jira/browse/CAMEL-26698
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-core
Reporter: Claus Ibsen
Fix For: 4.24.0
Camel counts the redeliveries and the failures handled by the error handler of
every route and every processor ({{ManagedPerformanceCounter}}:
{{getRedeliveries()}}, {{getFailuresHandled()}}, {{getExternalRedeliveries()}};
{{isRedeliveredHere}} credits a redelivery to the step that was retried). They
are only in JMX: the route dev console sends {{exchangesTotal}},
{{exchangesFailed}} and {{exchangesInflight}}, so the Camel CLI and the
terminal UI never see them.
So an exchange that failed and then succeeded on redelivery leaves no trace on
the Routes tab: the route shows 0 failed, and only the step shows
{{exchangesFailed}} for the failed attempts. Seen with a chaos rule
{{step=reserve error rate=0.1}} and a dead letter channel with 2 redeliveries:
the step had 46 failed out of 1761, the route had 0 failed, and the 132
redeliveries showed only on the chaos screen (from the chaos report, not from
Camel's own counters).
h3. Proposal
* The route dev console (route and processor statistics, JSON and text) adds
{{failuresHandled}}, {{redeliveries}} and {{externalRedeliveries}}, documented
with {{@Metadata}} like the other statistics; the catalog's dev console model
is regenerated.
* The terminal UI reads them (StatusParser) and shows them on the Routes tab:
for the routes, and per processor in the table under the route, so the step
that was retried is the one with the redeliveries.
* {{camel get route}} / {{camel get processor}} can show them too where it fits.
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
