Multinode agent monitoring
User is having a cluster setup.
User has configured Autonomic Event Services (AES) to monitor agents and listener on multiple nodes inside the cluster and configured webserver SOAP URL for URL of the node.
After doing so AES is fetching agent information from random nodes and this incorrectly presents the information about agents on a node.
Steps to Reproduce
- Click on a node from enterprise tab.
- Click on search agents.
These capabilities are not supported in the AES manager portal.
User has provided the correct URL to the AES server as a load balancer or web plugin URL and were monitoring many nodes ‘behind’ that IP address, which is not enough information for the AES server to gather specific information from the requested node.
Therefore user was getting the details from whichever server is used in accordance with the load balancer algorithm.
In this case, specific information can be ‘pushed’ from the monitored node only.
The AES server is not able to directly access the monitored node to make queries regarding the requestors or agents.
0% found this useful