@Tom_Eaton , Thanks for the response,
I think, I missed to add that, the process groups ‘process-1-1234-ab1c, process-2-5678-xy1z’ are detected via ‘advanced process group detection rule’ and because this rule, it keeps creating process groups like below,
process-1-1234-ab1c, process-1-3211-fd5j, process-1-3298-vbs5, and so on..
process-2-5678-xy1z, process-2-9845-ab1c, process-2-0121-ret3, and so on..
process-3-8765-xsf1, process-3-6544-q2we, process-3-5890-1aws, and so on..
.
.
.
and so on…
If I use ‘process naming rule’ to exclude content after second hyphen (-) for above process groups then, there will be lot of process groups with same name. If we take example for above case then, after applying process group naming rule it will be like below,
process-1, process-1, process-1, and so on.. (Process group)
process-2, process-2, process-2, and so on.. (Process group)
process-3, process-3, process-3, and so on.. (Process group)
.
.
.
and so on…
So process group naming rules will not help. We need to build a ‘process detection rule’ that will group a processes like below,
process-1 (Process group)
--> process-1-1234-ab1c, process-1-3211-fd5j, process-1-3298-vbs5, and so on.. (Process group instance)
process-2 (Process group)
--> process-2-5678-xy1z, process-2-9845-ab1c, process-2-0121-ret3, and so on.. (Process group instance)
process-3 (Process group)
--> process-3-8765-xsf1, process-3-6544-q2we, process-3-5890-1aws, and so on.. (Process group instance)
Regards,
AK