How the Data-Admin-Tenant table values are sourced.
The point where i got the issue is, my monitoring nde is shown as non up in the enterprise helth dashboard. the node is not able to get the agent listener and other information because the node is in unreachable state in AES. Further on investigation, Monitor Health Stats agent is using the values of the mentioned tenent class to get the values.
Could someone help me if you have faced the same issue
***Edited by Moderator Marissa to update platform capability tags***
Data-Admin-Tenant is not relevant to AES. If you look closer, it is only used when running PDC. The PDC service may be thought of as a multi-tenant version of AES, and we have to do some extra loops so that agents process in the 'tenant' context rather than default / shared context.
The AES "enterprise" UI is driven by health status messages that come from each node and are processed by the monitor Health Status agent. There is an assumption in AES that if a node is not sending health status data, the node is not working, so features that require sending data to the node, like fetching agent or listener status, are disabled.
Start by looking at pegaaes-data-nodestats -- is the node really sending data to AES? If you have access to the node, you can enable debug in classes httpclient.wire.content and httpclientwire.body -- do you see HLTH0001 messages being sent to AES?