[
https://issues.apache.org/jira/browse/CAMEL-25716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-25716:
-----------------------------------
Assignee: Claus Ibsen
> camel-management - remote exchange counters per route, for camel get
> processor --remote
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-25716
> URL: https://issues.apache.org/jira/browse/CAMEL-25716
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang, camel-management
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> The CamelContext has remote exchange counters (CAMEL-20879): the exchanges
> that came from a remote endpoint, such as Kafka or HTTP, apart from the
> internal ones (timer, direct). The routes do not, so camel get processor
> --remote, which shows the counters of the routes as remote/total pairs, has
> never had remote counters to show.
> Add the remote exchange counters to the routes (ManagedRouteMBean:
> RemoteExchangesTotal, RemoteExchangesCompleted, RemoteExchangesFailed,
> RemoteExchangesInflight), report them in the statistics of the route dev
> console, and show them in camel get processor --remote and camel get route
> --remote.
> A route whose consumer is remote has only remote exchanges, so its remote
> counters are its counters, at no cost. A route whose consumer is internal
> (direct, seda) counts the exchanges it processes that came from a remote
> endpoint, such as a direct route called by a Kafka route; an internal
> exchange costs one check per exchange.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
