davsclaus opened a new pull request, #29571: URL: https://github.com/apache/camel/pull/29571
Two fixes found while trying the chaos run option (#29567) on the timer-log example. ### The Errors tab has a row per kind of error The error registry keeps the newest 3 exchanges of each kind of error (route, node, exception type; `camel.errorRegistry.maximumEntriesPerKind`), and the Errors tab showed each of them as its own row. So one chaos rule failing `setBody1` gave 3 rows of the same error, with counts like 21, 22 and 23 for what was 23 failures. - One row per kind (route + node + exception, the same as the registry counts it). COUNT is the total for the kind, the title says how many happened: `Errors [1] 23 happened, a row per kind`. - The detail shows `Repeated: 23 times (since …)` and `Kept: exchange 3 of 3 (the newest)`. `[` and `]` step to the older or newer kept exchange, so their bodies and headers can still be compared. Shift+F8, `!` and the diagram act on the exchange the detail shows. - Integrations before Camel 4.21 have no counter: COUNT falls back to the number of kept exchanges. - `tui_get_table` still returns every kept entry. - Help page, user manual and tests updated. ### The timeline does not count the WARN camel-chaos logs when it is switched on When no exchange failed, the Timeline (and the "Last 5m" line of the About box, which reads it) takes the WARN and ERROR lines of the log as the cause. camel-chaos logs a WARN at startup to say it is switched on, so a fresh run with chaos showed `log WARN ×1` as if something went wrong. That line is no longer counted; camel-chaos still logs it as a WARN, and the Log tab still shows it. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_012nJsFsjqqFiwroeHRWaKbS -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
