Thanks Justin for the feedback. I will keep that in mind. On Fri 7 Jul 2023, 20:15 Justin Bertram, <jbert...@apache.org> wrote:
> The first thing I would recommend is to read the "Performance > Considerations" [1] section of the "Clusters" chapter in the ActiveMQ > Artemis User Manual. If you want to ensure that performance is close to > optimal (i.e. messages are not being moved around the cluster very often) > then you can monitor the internal store-and-forward queues which are used > for clustering. Essentially you just want to ensure that the MessagesAdded > metric for those queues is not continually increasing. Ideally it would > remain at 0. > > Aside from that I'm not sure I can give you any other advice on > specifically what to look for if you suspect clustering is causing a > problem. You'll just have to deal with specific use-cases as they arise. > > > Justin > > [1] > > https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#performance-considerations > > On Fri, Jul 7, 2023 at 4:47 AM prateekjai...@gmail.com < > prateekjai...@gmail.com> wrote: > > > Hi All, > > > > I am working on an application which is right now running a single > > instance of activemq. Now, due to increase in load and to improve > > availability; I am testing active/active cluster topology of activemq. I > > am successfully running a cluster (active/active) now. > > > > My question is, what are the key metrics that can be looked at from the > > observability perspective of this cluster. Basically, I am looking at > areas > > that can be looked at, if I suspect that it is clustering which is > causing > > the issue or, to prove that clustering functionality is not at fault. Any > > suggestions are welcome. > > > > > > Regards, > > Prateek Jain > > > > -------------------------------------------------------------- > > EXPECTATION : Causes all troubles...... > > -------------------------------------------------------------- > > >
