PEGA0082 events for unexpected queue processors
We recently updated to Pega Platform 8.6.4
PDC is reporting a number of PEGA0082 events, like
Data flow run [pyBatchIndexClassesProcessor] for data flow name [<not set>] started on node [adm-i-0507122fa25fe1c14] with partitions []
out of the box queue processor, and also for our own queue processors.
How can we eliminate these false positive events?
Accepted Solution
Updated: 6 Jul 2022 15:41 EDT
Blue Rose Technologies
NL
@PeterG0262
The alert PEGA0082 gets comes in pega-alert file whenever a data flow starts or resumes.
Many Out of the box agents have been converted to Queue Processor in latest versions and these QPs use Data Flows internally. So whenever the concerned node is restarted then this message is expected.
If these alerts are coming too frequently even though the nodes has not been restarted or the QP has not been restarted manually then for some reason the Data flows are going into pause state or stop state and then going to starting state. So in this scenario you can debug why this is happening or you can take help from Pega Support team to debug.