[
https://issues.apache.org/jira/browse/CAMEL-24911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-24911.
---------------------------------
Resolution: Fixed
> camel-core, camel-jbang - collapse identical repeated errors in the error
> registry and in camel_get_log
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-24911
> URL: https://issues.apache.org/jira/browse/CAMEL-24911
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.23.0
>
>
> When a route fails the same way for every message, the log and the error
> registry fill with identical entries: in one step of the camel-jbang-mcp
> stepwise benchmark a file consumer replayed three orders on every reload and
> each line failed the same HTTP call, giving 264 entries in the error
> registry, 132 of them for one URL, each with a full stack trace and message
> history. A model then reads 60 log records and sees nothing but repeats of
> one failure; a person tailing a dev log has the same problem.
> Collapse them: the error registry keeps one entry per (route, node,
> exception, message) with a count, first and last time, instead of one per
> exchange, and {{camel_get_log}} / {{camel get log}} folds identical
> consecutive records into one line with "(x132, 16:09:28 to 16:10:43)". The
> individual exchanges stay available (the console's detail view,
> {{camel_get_errors}} with a limit), only the default answer is folded.
> Related: CAMEL-24863 made the registry mark a copy handled when the original
> recovers; this is the volume side of the same data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
