# Metricbeat: How to monitor podman resources

**URL:** <https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [January 27, 2020, 8:25am UTC](https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619 "2020-01-27T08:25:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![giraffe](https://avatars.discourse-cdn.com/v4/letter/g/f1d935/32.png) [@giraffe](https://discuss.elastic.co/u/giraffe)\
**Post date:** [January 27, 2020, 8:25am UTC](https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619/1 "2020-01-27T08:25:28Z")

</div>

Hi Team

environment:  
CentOS 7.7  
metricbeat 7.5.2  
podman 1.4.4-4

I'm using podman ([https://podman.io/](https://podman.io/)) for run containers.  
Podman is a daemonless container engine for developing, managing, and running OCI Containers on your Linux System.

Please tell me how to monitor containers, such as monitoring cgroups directly without using docker api.

This page says it can be done, but I don't know how to set it.

[https://www.elastic.co/products/beats/metricbeat](https://www.elastic.co/products/beats/metricbeat)  
: It does this by directly reading the cgroups information from the proc file system, which means that it doesn’t need privileged access to the Docker API and works for other runtimes as well.

/etc/metricbeat/modules.d/system.yml  
cgroups: true  
process.cgroups.enabled: true

The above did not work.

best regards,

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [January 27, 2020, 9:57am UTC](https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619/2 "2020-01-27T09:57:16Z")

</div>

Hey!

You can use something like what you already tried. You can find more information about this [blogpost](https://www.elastic.co/blog/monitoring_container_resource_usage_with_metricbeat).

Also if you have Kubernetes involved you can use Kubernetes module directly.

C.

---

<div class="post-metadata">

**Author:** ![giraffe](https://avatars.discourse-cdn.com/v4/letter/g/f1d935/32.png) [@giraffe](https://discuss.elastic.co/u/giraffe)\
**Post date:** [January 28, 2020, 2:00am UTC](https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619/3 "2020-01-28T02:00:45Z")

</div>

Thank you for your advice.

The default settings were:  
process.cgroups.enabled: true

[https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-system.html](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-system.html)

And disabled other default settings below. It worked fine.

/etc/metricbeat/modules.d/system.yml:

```
# process.include_top_n:
# by_cpu: 5 # include top 5 processes by CPU
# by_memory: 5 # include top 5 processes by memory
```

I was able to get the value with kibana.

Thank you !

* * *

```
Dashboard [Metricbeat System] Containers overview ECS

Container CPU usage [Metricbeat System] ECS
"Container ID","Process name","CPU user"...
"libpod-56677f94b50a7cd0b4472a41b1ec6e16bda7e832a5f3c2c477339b47d799e0b0.scope","nginx","1,310,150,000,000"...

Container Memory stats [Metricbeat System] ECS
"Container ID","Process name","Usage"...
"libpod-56677f94b50a7cd0b4472a41b1ec6e16bda7e832a5f3c2c477339b47d799e0b0.scope","nginx","6447104"...

Container Block IO [Metricbeat System] ECS
"Container ID","Process name",Total,"I/O"
"libpod-56677f94b50a7cd0b4472a41b1ec6e16bda7e832a5f3c2c477339b47d799e0b0.scope","nginx","23126016,276"
```

---

<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:** [February 25, 2020, 2:00am UTC](https://discuss.elastic.co/t/metricbeat-how-to-monitor-podman-resources/216619/4 "2020-02-25T02:00:47Z")

</div>

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