Query for workload requests

Gibilisco — Thu, 19 Sep 2024 09:20:57 GMT

Hi,

I've noticed that the query used to show the CPU requests of a workload from the workload entity page is like the following one.

builtin:kubernetes.workload.requests_cpu:filter(eq("dt.entity.cloud_application",CLOUD_APPLICATION-D208D96CD2DA8E7A)):splitBy("dt.entity.cloud_application"):sum

What is the rationale behind the latest split by and aggregation?
A simpler query like the following one provides the same results but I'm not sure there are corner cases which I'm not seeing.

builtin:kubernetes.workload.requests_cpu:filter(eq("dt.entity.cloud_application",CLOUD_APPLICATION-D208D96CD2DA8E7A))

Thank you.

Re: Query for workload requests

p_devulapalli — Fri, 20 Sep 2024 01:34:12 GMT

I think both the queries would provide you with a similar result in this case , just that the first one is a autogenerated when you open it Data explorer from workload entity page. The splitBy and aggregation may not make much deference in this specific case as you are already filtering it to a specific workload and the value returned is very constant.

the aggregation might make a difference in other use cases if you choose metrics like CPU usage or CPU throttling

topic Query for workload requests in Container platforms

Query for workload requests

Re: Query for workload requests