Monitored Nodes behind a LB VIP
I get below Alert in my AES for the Production Systems. While the monitored nodes send the alerts,exceptions and Health messages, the issue is AES cannot communicate with Monitored nodes, as the nodes are not exposed directly. The nodes are behind a Load Balancer VIP. Did anyone face similar issue and how did you silence this valid alerts or any workaround for this kind of Monitored nodes setup?
Verify that the monitored nodes in this system are operating and reachable, so that this AES server can retrieve index information from them
Pegasystems
IN
AES 7.1.7 supports only one way communication between monitored nodes and AES. This can avoid the issue of AES having to talk back to the monitored nodes and thus having to go through the load balance. The same is the case if you use the Predictive Diagnostic Cloud as well. Please reach out to Pega support or your account executive for further details on this.
Amazon Corp
US
We are already on AES 7.1.7. When I talked to Pega support, they said there is no OOTB way of avoiding AES to Monitored nodes communication and eventually those errors. Did you have such use case and were you able to silence these?
Pegasystems
IN
If your monitored nodes are Pega 7.1.6 or above, then setting the following Data-Admin-System-Settings instance "aessetting/perfstatmode" to "PUSH" should make it one way.
Alternatively, on the AES side, you can go to the administration tab in the aes manager portal and disable the callback to the monitored nodes. Please see screenshot below.
Amazon Corp
US
I did this change, but it still complains that Index Information Could not be retrieved. Is there perhaps an override setting that is nullifying this as the description clearly says that the remote index info collection disabled.
Pegasystems
IN
You might want to restart the agents after this change for immediate effect. If that still doesn't work, I suggest you raise an SE item for the team to investigate further.
Pegasystems
IN
You may also refer to this mesh discussion - https://mesh.pega.com/message/180456#180456