ARTEMIS-2777 Add core federation and broker connections to the management console
This is a bit out of the blue but basically it has been bugging me how outgoing connections aren't able to be managed in Artemis for anything but Bridges. So I looked into adding something similar primarily for federation but also for the AMQP broker-connections. Simply displaying the configuration didn't seem useful so similar to Bridges i tried to pull up some attribute related to the actual state, for AMQP broker-connections, i exposed if the connection was actually open. For core federations I added visibility into the upstream consumers that are generate from the policy and a message count for messages they have transferred back.
I was just thinking about this. This looks like a great contribution.
@tabish121 & @clebertsuconic, is there anything else you think needs to be included in this?
Core Federation is essentially unmaintained (and under tested) and should probably be marked as deprecated for removal in a future release. Given that I'd say adding management APIs and code for it seems ill advised.
Core Federation is essentially unmaintained (and under tested) ?? Why do you say this? I mean i don't see any large bug tickets, and its used in a number of commercial bank systems.
Should I remove the core federation management code and mark the core federation API's deprecated and point developers to the AMQP federation then?
Thanks @tabish121 for reimplementing this for broker-connection in https://github.com/apache/activemq-artemis/pull/5347. I have tried it out on the latest 2.39 release and am happy with it so I will close this change and the related ticket since i am okay with switching to broker-connection federation for my use cases.