I have the following use case, multiple process running with different arguments :
/bin/bash ./testDynatraceLog.sh -help -file=/tmp/projet1 /bin/bash ./testDynatraceLog.sh -help -file=/tmp/projet2 /bin/bash ./testDynatraceLog.sh -help -file=/tmp/projet3
I have in the top consumers, the process group : "bash"
I would like to separate the process are the do not belong to the same project :
I created a "Declarative process grouping" : MyBatchProcess, with the rules :
MyBatchProcess-project1 MyBatchProcess-project2 MyBatchProcess-project3
Solved! Go to Solution.
Be careful not to mix things.
Declarative grouping, used in your first part, does not work for processes that have deep monitoring enabled. So fits the purpose you try to achieve.
Advanced process group detection rules, as I think you use in the second part, enable you to adapt the detection logic for deep monitored processes, only. And that does not apply.
You will have to stick to Declarative Process grouping, with its limitations.
If your "projectN" instances are a fixed set, you can add an entry for each.
I however advise to go by the API path then, especially if there are more then 3 entities.
Unfortunately regex and such to match on every possible occurrence is not possible yet.
I was thinking of the DT_CLUSTER_ID environment that you could set, but I think that only works with deep monitored processes.
Also have a look at this topic: