Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

Not Applicable

Steps to Reproduce

  1. Click on a node from enterprise tab.
  2. Click on search agents.

Root Cause

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.


Published March 17, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us