davsclaus opened a new pull request, #27189:
URL: https://github.com/apache/camel/pull/27189
_Claude Code on behalf of davsclaus_
While the integration runs, the Source tab shows, at the end of each line,
what the processors on it do:
- the exchanges they handled: `● 79`;
- how many failed: `✗ 10`, in red;
- their mean time, when it is 1 ms or more.
The numbers follow the running integration, so the source reads as a heat
map of the route: where the messages go, and where they fail. Tested live on a
timer route with a filter and a `throwException`:
```
7 | from("timer:tick?period=500") ● 79 ✗ 10
9 | .setBody(simple("${random(10)}")) ● 79
10 | .filter(simple("${body} > 3")) ● 79
11 | .to("log:big?level=OFF") ● 52
13 | .choice() ● 79 ✗ 10
15 | .throwException(new IllegalStateException("nine"))
● 10 ✗ 10
17 | .to("log:tick?level=OFF"); ● 69
```
### How
- The status the TUI polls already has every route's processors with their
statistics. `StatusParser` now also keeps each processor's source location
(`source`, `file:line`, which `camel run` records).
- `LiveRunLines` adds up, per line of the file shown, what the processors on
that line did. Totals and failures are summed, and the mean time is weighted by
the exchanges. The route itself goes on its `from` line.
- The viewer draws it after the jump links. It reads the data at most once a
second.
Nothing changes for a project that is not running, and plain mode (`p`)
leaves it out.
New test: `LiveRunLinesTest`. The full TUI module (1459) passes. F1 help and
the TUI doc page are updated.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
