Product enhancement - Need for Out-of-the-box Rule-Agent-Queue instances to be placed under unlocked Rulesets
Our customer would like to disable specific Rule-Agent-Queue instances (e.g. - PegaAES and Pega-DecisionEngine) which are redundant for their application / environment. However, this is impossible as these Rule-Agent-Queue instances are under locked Pega Rulesets. They have urged the need that the Pega platform should have a way to disable Rule-Agent-Queue instances rather than Data-Agent-Queue instances. Because of this flawed designed they had a production outage which needed a change to the generated Data-Agent-Queue instances and the entire cluster of 57 JVMs had to be restarted.
They expect a product design change or an alternate solution to this so that any future outages can be mitigated.
***Moderator Edit-Vidyaranjan: Content edit, Tagged FDBK ID & SR details***
A feedback request has been created on the users behalf on our internal portal. You can share the feedback request ID with the user. They can use the FDBK ID as reference and connect with their Pega Account Executive to track the progress of the request.
The FDBK ID has been tagged along with the issue description.