davsclaus opened a new pull request, #29600:
URL: https://github.com/apache/camel/pull/29600
_Claude Code on behalf of davsclaus_
**Stacked on #29599 (CAMEL-26823)**: retarget to `main` once that one is
merged.
About read how the routes reach each other from the sources, by scheme, so a
hop over a broker between the routes of one integration was a message from
outside. connect-service/jms-request-reply had its queues as both In and Out,
all six routes at the top, and 14 exchanges for 3 orders.
**Before**
```
In: file:orders, jms:queue:orders, jms:queue:stock, jms:queue:orders.dead,
jms:topic:orders.reserved ×2
Routes: order-intake, reserve-order, stock-service, dead-orders, shipping,
invoicing (all at the top)
Out: jms:queue:orders, jms:queue:stock, jms:topic:orders.reserved,
jms:queue:orders.dead
Last 5m: 14 exchanges · 1 handled
```
**After** (live, on a build with #29599)
```
In Routes
Out
📁 file:orders 3 order-intake file → 4 steps 3
nothing outside the integration
⇢ reserve-order jms → 6 steps 3
↳ stock-service jms → 5 steps 3
⇢ shipping jms → 1 step 2
⇢ invoicing jms → 1 step 2
⇢ dead-orders jms → 1 step, on failure 1
Last 5m: 3 exchanges · 1 handled
```
- New `RuntimeLinks`: for a running integration, About takes the links from
its route topology (the one the Diagram loads, cached until a reload), whatever
the component: a route the sender waits for (`reply`: direct, a request-reply
over JMS) is a call `↳`, one it hands the message to (seda, a topic, a wire
tap) a hand-off `⇢`, and an error path (a dead letter queue) a hand-off marked
`on failure`.
- In and Out leave out a destination only the integration itself sends to or
consumes. One that others send to as well stays as an In with what they sent,
from the in and out hits of the endpoint: `jms:queue:orders +5 from outside`.
- Last 5m and "since it started" count a message once: a call is part of its
caller's exchange, a hand-off counts only what went wrong there, as for direct
and seda already.
- An opened project that does not run, and an integration that does not
answer, keep the links of their sources.
- Help of the Overview and the TUI observe page.
Also checked live: connect-service/mqtt (`sensors ⇢ cold-rooms` over the
MQTT topic, 48 exchanges for 49 readings instead of about twice that, the topic
no In or Out) and route/enrich-and-dedupe (`audit` under `incoming-orders` over
its wire tap, which the topology has as an edge with #29599).
Tests: `RuntimeLinksTest` (the jms-request-reply topology: the tree, In and
Out, `+N from outside`, an out of the runtime on a queue of the integration, no
topology). The TUI suite passes locally.
🤖 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]
