22 Jan 2024 07:40 AM - last edited on 23 Jan 2024 03:00 PM by Michal_Gebacki
Hello,
I want split process group to each Process per host.
My service naming rule running success with process no group, it show: :8081 on k8s-node04
But with process have group it show :8081 on k8s-node04, k8s-node05, k8s-node06
I've try to create rule service detection but it can't split. Can anybody help me!!
Solved! Go to Solution.
22 Jan 2024 07:42 AM
22 Jan 2024 08:53 AM
Hi @tuanla123
It seems to me that you have a badly made process detection rule. Have you tried setting Process group naming rules yet ?
Radek
22 Jan 2024 09:07 AM
I've try show with host but it still show many name of 1 process group. I just want separate per host
22 Jan 2024 09:19 AM
I'll look at it later, as I have meetings scheduled now, and I'll let you know:)
22 Jan 2024 10:08 AM
TBH, I'm not sure if this is really what you need. You still have process group instances within the process group which you monitor individually. Unless each instance is in charge of a different set of requests, I'd strongly advise not to split it. If those nginx processes are part of a pool, you want them to be in a single process group.
22 Jan 2024 10:23 AM
I want split it because I want to see each process with its host
22 Jan 2024 10:27 AM
You already have the node information there. Where do you miss the host name? On a dashboard?
22 Jan 2024 10:28 AM
yes, but it contain many node on 1 process group. I want show 1 process with its host like
nginx:8080 k8s-node.01
22 Jan 2024 10:36 AM
You can get the host name using the :parents transformation, see this example:
Is this what you want?
The process group represents an application "cluster" of processes. If the nodes are functionally equal and process the same workload, it should be the same process group.
22 Jan 2024 10:39 AM
oh, So is there any way to handle that?
22 Jan 2024 11:44 AM
@tuanla123 yes you can split it still using process group detection rules for example as stated above.
Anyway, I still believe the same k8s workload should be within one process group so you can look at it as a cluster of nginx processes.
23 Jan 2024 02:18 AM
can you guide me to create the rule ?