# Metricbeat metricset in kubernetes module

**URL:** <https://discuss.elastic.co/t/metricbeat-metricset-in-kubernetes-module/184783>\
**Category:** Beats\
**Tags:** beats-module, metricbeat\
**Created:** [June 7, 2019, 4:06pm UTC](https://discuss.elastic.co/t/metricbeat-metricset-in-kubernetes-module/184783 "2019-06-07T16:06:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhblair](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@bhblair](https://discuss.elastic.co/u/bhblair)\
**Post date:** [June 7, 2019, 4:06pm UTC](https://discuss.elastic.co/t/metricbeat-metricset-in-kubernetes-module/184783/1 "2019-06-07T16:06:41Z")

</div>

Hi, all. I'm newby to ES and kibana.  
This is the very first time to use ES with k8s-module, but I don't have any clue.  
I need any help, please. ☹

I'd like to bring the same value as the example below, "resource-quota per namespace in the k8s cluster" and visualize them on the kibana dashboard.

For example,

_$ kubectl describe quota -n {user-namespace}_

Name: resource-quota  
Namespace: {user-namespace}  
Resource Used Hard  
========================================­­  
requests.cpu 400m 4  
requests.memory 500Mi 4Gi

Since daemonset cannot be distributed due to resource problems, only the metricbeat deployment will be used.

I collected the value of container cpu requests, aggregated them with id, and then grouped them by namespace.  
When the container was regenerated or redistributed, the container id was newly created, and the request of the deleted container was also accumulated, so the exact value could not be obtained.

What is the exact metricset-field name for getting "Used" value of requests.cpu/memory ?  
Should the required metricset be included in daemonset...?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [June 13, 2019, 7:32am UTC](https://discuss.elastic.co/t/metricbeat-metricset-in-kubernetes-module/184783/2 "2019-06-13T07:32:35Z")

</div>

Hi @bhblair!

And welcome to the forum!

We have an open issue to add resource quota info, check [https://github.com/elastic/beats/issues/6659](https://github.com/elastic/beats/issues/6659)

As per cpu/memory usage, this is retrieved by the DaemonSet, as it is requested from the local kubelet node. `pod` and `container` metricsets get those.

Best regards

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 11, 2019, 7:32am UTC](https://discuss.elastic.co/t/metricbeat-metricset-in-kubernetes-module/184783/3 "2019-07-11T07:32:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.