Dear All,
I am facing a challenge while renaming processes groups. I tried both manual and naming rules methods but with no success.
In the below screenshot (the latest screenshot after applying the 2 naming rules, 1 for int web servers and 1 for ext web servers), you can see that hostnames are different. 2 hosts starting with the http (internal web servers) and 4 hosts starting with the rolh (external web servers).
If I change the process group name to ext/int web servers' it applies to all processes groups instead of the relevant host processes.
Regards,
Babar
Answer by Paco A. ·
Hi,
Probably you need to approach using different host groups , this way Dynatrace will separate in different process groups and from here you can start to apply renaming rules.
Another thing you can try is "Process group detection rules" to separate process groups.
Regards,
Paco
Hello @Paco A.
Thank you for your comments.
Please elaborate a little more the point number one, which I totally could not understand.
These are Apache processes, and all are 100% similar. Detection rules are not going to make any difference, in my opinion.
Regards,
Babar
@Babar Q.
Process groups may be hard to finetune if the detection fails in your case. You have two rules:
- detection rules - define processes that would make a process group
- naming rules - defined naming for detected process groups.
If in a process group you have processes (web servers in your case) from different "clusters", then you need to use detection rules to separate the process groups.
If you want to rename an existing process group, you can use the naming rules, or manually change the name in the process group setting for a particular one. All process group instances from this process groups will be renamed.
I guess in your case, you need process group detection rule. It depends on your environment, but most likely you can differentiate those either on a process property / command line arguments, etc. If you cannot differentiate those on any property, you can always add a new environments property (DT_CLUSTER_ID / DT_NODE_ID) to separate it.
Hello @Július L.
Thank you for your comments.
As you can see that properties and command line args are the same for both Ext/Int web servers. There is nothing to use detection process rule to distinguish them (if my understanding is correct).
![]() |
![]() |
As I mentioned in my starting comments, manual, or automatic renaming applying to all process groups (external and internal).
Do you think that now I left only with the new environment property (DT_CLUSTER_ID / DT_NODE_ID) to separate it?
Regards,
Babar
Apart from what you can see, there still might be an environment variable (not visible in the process properties) you can use in process group detection rule.
Or you can introduce DT_CLUSTER_ID and DT_NODE_ID and set the process group name directly. I can see you are using IHS (apache). In a typical deployment, you should put those variables in the envvars file in the IHS directory. (Your case might still be different).
Your problem now is that all process seems to be detected under same process group, so any process group naming applies to all the processes. So you need 1st to separate those processes in different process group and once you have it separated you can apply process group naming.
You have 2 different strategies.
Host groups affect how process groups are detected. When the same process is running in two different host groups, Dynatrace will create one process group for each host group.
Hope this help.
regards,
Paco
Hello @Paco Porro A.
I used the combination of host groups + process groups but no luck. Yes, they distributed between different host groups.
Everything is the same, including Exec name, Exac path, Command line args, etc.
Regards,
Babar
Hello @Paco Porro A.
Apologies in advance if I could not understand your point correctly. Do you mean restart after the logical naming of process groups?
Regards,
Babar
JANUARY 15, 3:00 PM GMT / 10:00 AM ET