[ 
https://issues.apache.org/jira/browse/ARTEMIS-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839378#comment-17839378
 ] 

Erwin Dondorp commented on ARTEMIS-4182:
----------------------------------------

[~jbertram] 

The screenshot is already in the description. The image shows that 
cluster-connections do not fill the column ClientID,

The remote address column indeed shows the ip-number of the remote node. But 
(for me) these ip-numbers are assigned dynamically. From these ip-numbers, I 
cannot determine which node did not connect to the cluster. e.g. Assume the 
screenshot is from a 6-node cluster. The "own" node (where we are viewing from) 
is never in the list, but which one of the other 5 nodes is not connected and 
therefore not in this list? To answer that question, I must either lookup the 
ip-addresses and eliminate the good ones to find the missing one, or open the 
consoles of all 5 other nodes.

> fill client-id for cluster connections
> --------------------------------------
>
>                 Key: ARTEMIS-4182
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4182
>             Project: ActiveMQ Artemis
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 2.28.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>         Attachments: image-2023-02-25-13-27-08-542.png
>
>
> when running Artemis in a cluster, the brokers have connections between them.
> these are easily identifiable in the list of connections because the "Users" 
> field is filled in with the username that was specified in setting 
> `cluster-user`.
> but it is unclear where each connection goes to.
> !image-2023-02-25-13-27-08-542.png!
>  
> additional information:
> the field "Client ID" is filled in with the remote hostname when using 
> broker-connection/amqp-connection.
> wish:
> (also) fill in field ClientID of the cluster connections.
> e.g. with the broker-name or from a new parameter `cluster-clientid`



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

Reply via email to