You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Serdar Gökay (Jira)" <ji...@apache.org> on 2026/10/21 08:31:00 UTC

[jira] [Created] (CAMEL-25913) camel-milo - add a dev console that lists the connections and their refused monitored items

Serdar Gökay created CAMEL-25913:
------------------------------------

             Summary: camel-milo - add a dev console that lists the connections and their refused monitored items
                 Key: CAMEL-25913
                 URL: https://issues.apache.org/jira/browse/CAMEL-25913
             Project: Camel
          Issue Type: Improvement
          Components: camel-milo
            Reporter: Serdar Gökay


h3. Problem

When the server refuses to monitor a node, the {{milo-client}} consumer reports it once: a WARN and one exchange with the refusal status. With CAMEL-25692 the node is created again every 10 seconds, but nothing shows its state after that: later attempts and their failures are logged at DEBUG only, while the connection and the route look healthy. Someone who missed the first WARN cannot tell which nodes are not monitored, or why.

A health check is not the right place: a refused node is a problem of that one node, usually its configuration, and a check that goes down for it would mark the whole application unhealthy, for example take it out of service, without fixing the node.

h3. Proposal

A read-only {{milo-client}} dev console that lists, for each connection:
* the endpoint and whether its session is active;
* the number of monitored nodes;
* the refused nodes, each with the status of its latest attempt: the refusal by the server, or the failure of the attempt.

Reading it must not wait for a service call that holds the manager lock.

h3. Related

Agreed in the review of CAMEL-25692 ([#28212|https://github.com/apache/camel/pull/28212]), questions 1 and 2.

I can send a PR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)