Applies to all cloud-managed environments.
Scenario
The user is unable to view the nodes and rulesets in Agent landing page within Admin Studio wherein the agents are running.
Explanations
This behavior is expected for environments wherein nodes or containers are managed by a controller such as Kubernetes, Pega Cloud or client-managed cloud.
As shown in the figure below, in such scenarios the rows cannot be expanded (accordions are not present) to display the node-specific data to the user.
This is because the node IDs are not static between node restarts in these environment configurations.
For users on client-managed VM environments, Admin Studio System settings page shows the nodes that are defined. Refer to the figure below:
This is because the node IDs are static between node restarts in these environment configurations.
Best practice
Since Agents are depreciated, job schedulers should be used instead of advanced agents, and queue processors should be used for older agent queue definitions.
Related content
- Managing system resources (Pega documentation for Pega Platform 8.7)
- Managing system resources (Pega documentation for Pega Platform ’24.1)
- Using job schedulers and queue processors instead of agents