Cannot see Agent in System - > Operations - > Agent Management screen
This has been observed in our 7.3.1 environments with the System -> Operations -> Agent management screen. We have 105 Agent jobs available but seem to only see about 90 of them. Applying filters doesn't seem to requery the list and supply the missing agent jobs. This was noticed as the default list seems to be alphabetic by agent name and the one I was looking for begins with "V". I was unable to see beyond a job called "UpdateXXXX" in our Agent listing and counted about 90 records in the intial screen. Is this W.A.D.? Is there another setting I should be using? (I did go the old fashioned route and look for the Agent Schedule record to do what I set out to do, but I can't trace from that screen). Aside from "you shouldn't be running 105 agents ..." is there an answer to this issue?
***Edited by Moderator Marissa to update platform capability tags***
Wells Fargo N.A.
US
Let me adjust the scope a bit. I'm attaching two screen shots focused just on the PegaAESRemote ruleset and what I can/can't see. SysOpsAgent_PegaAESFilterApplied_Capture.JPG shows what the Pega 7.3.1 Agent management screen tells me about PegaAESRemote agent processes (i've applied a filter on the ruleset field to limit the scope to the PegaAESRemote agents). SMA_PegaAES_Capture.JPG shows the same system, same node, information on PegaAESRemote agents running. As you can see it is more agents than I'm able to view on the new Agent Management screen in 7.3.1. I don't see any pagination on that screen, so I'm assuming it's just being limited somewhere and somehow.
Pegasystems Inc.
US
First screen shot is agent status from one node, listing several agents in PegaAESRemote
Second screen shot is the status of the initialize health info agent noting that it is running on three nodes
Wells Fargo N.A.
US
That's correct. But what's missing in the second screen shot are the 3 other PegaAESRemote agent processes that should show up (PushLogUsageData, PushDBIndexes, PushGuardrailData). And outside of the PegaAESRemote agent, there are others that aren't appearing. That's the point I'm trying to make - when SMA goes away if all your agents are accounted for in the new Pega Agent Mangement screen ... how are you going to manage them?
Wells Fargo N.A.
US
So, are you saying these Agents will only show on a node Typed as "UTIL"? So, we need to type our nodes just to see the Agent? Again, I'm not even caring about running or not here ... in the Agent Management screen I can fully stop all instances of an agent and still see it out there. I want to know that ... similar to the current functionality in SMA .. all Agents running or not can be managed via a UI. If I can't see the Agent exists, how can I start, stop, or trace it to analyze what's wrong with it.
Might this have to do with Agent Schedules? Is it possible if an Agent is non-important or doesn't have an Agent Schedule created on any node that it might not appear in the Agent Management screen?
Pegasystems Inc.
IN
Check how many counts you have in pr_index_rule_agents table and those records .
And Agent Management shows values from the pzAgentNodeManagementInner section and it have the pagination set .
Wells Fargo N.A.
US
Agreed Arun. I'd seen the pagination setting, but even removing the pagination doesn't get me everything I can see in the SMA screen.
I'm just saying - if Pega plans to make this Agent Management screen the SMA Agent replacement, I should be able to see all the Agents. Unless there's some filter/reason why I shouldn't - and if that's the case then I would love to know what that reason is for the exclusion. Like I said - I can only see 1 of 4 PegaAESRemote agents and I can't explain why that is the case.
Wipro
IN
I was facing the same issue and I found how we can see all the invisible agents. This is clearly a bug in pega which I hope they will fix. To see the invisible agent access the application through the node where the agent is running and then open the systems operations-> agent management->node you will be able to see that agent there and that can be traced from there.