Question
Pega Systems
IN
Last activity: 28 Nov 2017 14:19 EST
Monitor and Notify when Agent disabled
We have a few agents running and we want to monitor only those.
SMA and agent Management landing page provides list of all agents and we need to manually go and check for our specific agents - if we want to monitor.
Also another thing to look at - Alert Pega0010 when agent is disabled.
Configured AES to notify on manage subscriptions to send a mail on agent disable.
What we want is - to be able to track only specific set of agents that we are critical and send a mail alert on this event.
What should be the ideal way to get this? Declare Trigger when alert Pega0010 is populated? or On DB side have a trigger??
***Edited by Moderator Marissa to update categories***
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
IN
Hi,
You can use the value of StepStatusGood in your agent activity and use SendEmailNotification activity for sending the message when it goes down. Also, you can add log message as well.
Also refer the below discussion if above doesn't work should be helpful
https://collaborate.pega.com/question/send-notification-when-agent-gets-disabled
Thank You
ANZ Banking Group Ltd
AU
Hi
I will suggest you to go with Declare Trigger when alert Pega0010
because with this option you configure the notifications or any specific task if the alert is added .
if you go with DB side you may not have that flexibility
Accepted Solution
Pegasystems Inc.
US
When an agents fails, PEGA0010 alert is written to log file and optionally sent to AES / PDC. In the Pega platform, there is no class to store alerts, so you can't capture it with a rule declare trigger.
In AES, PEGA0010 alerts are stored as instances of PegaAES-Data-Alert, and various decision tables are used to assess that it is a critical alert and the Agent failure scorecard should be sent immediately.
I imagine one could enhance AES to add a new scorecard for a specific agent failure, and then send that scorecard to parties interested in that particular scorecard.
Out of curiosity - why not send scorecards for all agent failures? Are there specific agents that are expected to fail in production? Is there any reason to ignore certain agents failing?
Pega Systems
IN
Great question, not really there is any OOTB agent that we want to ignore.
But, somehow we saw in recent past - our app specific agents only going down, not frequently though. Every time user sees that they are not getting their work objects (there is an agent that we created - used to get work from the legacy system and seed into Pega). By the time we get to know about this issue, it is usually 3-4 days for various reasons. And the simple go to is - to check if the specific agent is running and most of the times the agent went down.
As rightly mentioned by you, I believe its definitely a good enhancement to have a new scorecard for the specific agent failure.
Pegasystems Inc.
IN
Hello!
Do let us know if there needs to be a product enhancement request to be filed for this!
Regards,
Pega Systems
IN
It is definitely be a good to have feature.
When an agents fails, PEGA0010 alert is written to log file and optionally sent to AES / PDC. In the Pega platform, there is no class to store alerts, so you can't capture it with a rule declare trigger.
In AES, PEGA0010 alerts are stored as instances of PegaAES-Data-Alert, and various decision tables are used to assess that it is a critical alert and the Agent failure scorecard should be sent immediately.
I imagine one could enhance AES to add a new scorecard for a specific agent failure, and then send that scorecard to parties interested in that particular scorecard.
Out of curiosity - why not send scorecards for all agent failures? Are there specific agents that are expected to fail in production? Is there any reason to ignore certain agents failing?