davsclaus opened a new pull request, #29510: URL: https://github.com/apache/camel/pull/29510
_Claude Code on behalf of davsclaus_ Found by running the `showcase/message-size` example: three timers, each feeding a seda queue that another route of the integration consumes. The Endpoints tab's Flow panel said `50 in → 25 out` for 25 messages that never left the integration, and the in rate of its chart was twice that of the timers. **Cause:** the flow added up every endpoint by direction. An endpoint one route of the integration sends to and another consumes (`direct`, `seda`) is a hand-off between its routes, and it was counted twice: once as the out of the sender and once as the in of the consumer. Since CAMEL-26780 (#29476), a route called over `direct` also counts its input, so any integration with a `direct` call doubled too. **Fix:** `EndpointFlow` finds the hand-offs, meaning the endpoints the integration both sends to and consumes, and the Flow panel and the in/out rate chart leave them out. The example now shows `21 in → 0 out` (its timers) and an in rate of about 1 msg/s. The table still lists every endpoint. The remote filters were already right, as internal endpoints are not remote. The avg body chart is unchanged: message sizes per endpoint, seda included, are what that chart is for. The help page (endpoints.md) says so. Tests: `EndpointFlowTest`. The full `camel-jbang-plugin-tui` suite passes, apart from `ConfigurationTabRenderTest`, which fails on main and is fixed by #29503. I checked it live with the example. 🤖 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]
