I had pretty much the same problem, as it's not just the toggles but also metrics which aren't available for the entire cluster. I ended up building "a JMX proxy", which aggregates metrics from all available nodes, and offers the results via its own JMX interface. This way I can control the cluster from a single JConsole or JMC instance, and hook it up to Zabbix for monitoring and alerting. Perhaps not the fanciest approach but it's extensible and "good enough".
Jan ________________________________ From: Justin Bertram <jbert...@apache.org> Sent: Wednesday, May 22, 2024 6:02:23 PM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: Single web-console for artemis cluster I'm not aware of any existing plans to build a single web-console for a whole cluster. At first glance this seems like a big chunk of work for relatively little upside. Switching between browser tabs to manage different brokers may be a bit tedious, but it is simple and effective. What specific tasks are you performing most often? Perhaps there are other ways to accomplish these tasks that would be more streamlined. Justin On Wed, May 22, 2024 at 6:35 AM Назар Фатихов <nazar.fatik...@gmail.com> wrote: > Hello all, > > We configure ActiveMQ Artemis cluster and find it a bit inconvenient to use > multiple web-consoles for each broker instance to manage it. Do you have > any plans regarding a single web-console for the whole cluster? Either > would you point me to the related topic which I can subscribe to if there > is any? It seems to be easier to manage clusters using a single > web-interface and not switching between different interfaces per each > broker instance. > > Thank you for work and support, > Nazar Fatikhov >
