How to monitor nodes in hazelcast high availability cluster
Hello everyone!
I would like to know what the correct way to monitor the number of nodes in a Pega high availability hazelcast cluster is. I would like to setup alerts to be informed whenever a node leaves the cluster so we can act on it before the current and pending JMS message queues disrupt the cluster.
So far I have found only three ways to monitor the nodes in a cluster:
1 - Hazelcast management center
I have found this article (https://community.pega.com/knowledgebase/articles/deploying-hazelcast-management-center) explaining how to setup the hazelcast management center so we can monitor the cluster, but it seems this is only available for Pega 8.4 and later using the client-server model. We use Pega 7.3, so it does not apply.
2 - 'Members' REST service
In Pega there is a service called 'Members' in the 'Operations' package in the Pega-SystemOperations RuleSet that seems to do exactly what I want, but it has been withdrawn.
3 - Monitor changes in the PegaCLUSTER.log file
As far as I understand it, whenever there is a change in the cluster composition, all nodes (Except the one that left the cluster) update their PegaCLUSTER.log file with the new information. This approach would require monitoring these files and I would like to avoid it if a more direct solution exists.
Hello everyone!
I would like to know what the correct way to monitor the number of nodes in a Pega high availability hazelcast cluster is. I would like to setup alerts to be informed whenever a node leaves the cluster so we can act on it before the current and pending JMS message queues disrupt the cluster.
So far I have found only three ways to monitor the nodes in a cluster:
1 - Hazelcast management center
I have found this article (https://community.pega.com/knowledgebase/articles/deploying-hazelcast-management-center) explaining how to setup the hazelcast management center so we can monitor the cluster, but it seems this is only available for Pega 8.4 and later using the client-server model. We use Pega 7.3, so it does not apply.
2 - 'Members' REST service
In Pega there is a service called 'Members' in the 'Operations' package in the Pega-SystemOperations RuleSet that seems to do exactly what I want, but it has been withdrawn.
3 - Monitor changes in the PegaCLUSTER.log file
As far as I understand it, whenever there is a change in the cluster composition, all nodes (Except the one that left the cluster) update their PegaCLUSTER.log file with the new information. This approach would require monitoring these files and I would like to avoid it if a more direct solution exists.
Option 2 could be used if I save the rules involved to another ruleset, but since I don't know why they have been withdrawn (Security? Performance? Better alternative has been developed?), I would like to know what the recommended solution to this is.
Thank you in advance.