We have a pod and want to test the monitoring of the limits of pods that should be running (Max, not min). Try it with the custom alerts under the process (for all instances) but it dont "add up" the number of process running. And selecting the Process Group shows the metrics empy. So no metric could be selected.
Is there any way to do this?
Solved! Go to Solution.
Hi @Andre van der V. Yes, i notice that. for me it was 6 all the time. I actually managed to make it kinda work, but it forced me to "Strip" the concept of docker at process level and unite all the pods under a same process (no pod name or id).
In that case i notice that the Pods running was actually the detected Workers for that process, 3 pods = 3 workers and so on... But that was not use since all the information about the transactions for an specific pod was missing. And also couldnt split the transactions metrics per pods. Either.
Got this back from support:
The "Process process count" metric is the number of PIDs concurrently running per PGI, not the number of PGIs per PG.
Regarding the empty metric list for "Process Group": there aren't any built in metrics on PG level. So unless there are any custom plugins which define custom metrics on PG level, the metric list will be empty, when selecting "Process Group". As this might be confusing, we redesigned this screen (currently being implemented)