# Metricbeat Podman Container Metrics

**URL:** <https://discuss.elastic.co/t/metricbeat-podman-container-metrics/379212>\
**Category:** Beats\
**Tags:** docker, metricbeat\
**Created:** [June 16, 2025, 3:57pm UTC](https://discuss.elastic.co/t/metricbeat-podman-container-metrics/379212 "2025-06-16T15:57:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![shabpa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shabpa/32/143684_2.png) [@shabpa](https://discuss.elastic.co/u/shabpa)\
**Post date:** [June 16, 2025, 3:57pm UTC](https://discuss.elastic.co/t/metricbeat-podman-container-metrics/379212/1 "2025-06-16T15:57:07Z")

</div>

Hi everyone,

I'm currently running **Metricbeat inside a Podman container** , and I'm trying to collect metrics from other containers.

So far, I'm successfully receiving data from the following metricsets:

- `cpu`
- `network`
- `container`

However, I'm running into issues with the following:

- The `diskio` metricset is present, but **all values are zero**.
- The `memory` and `info` metricsets are **not returning any data at all**.

Interestingly, I'm also getting metrics from the **`system` module** (that is not even configured in the `metricbeat.yml`) , and **all metricsets are working fine**. This includes CPU, memory, filesystem, and disk metrics.

My setup:

- Metricbeat version: 8.17.7
- Metricbeat is configured with the `docker` module enabled and pointed to the Podman socket (`run/user/$USERID/podman/podman.sock` is mounted into the container).

I’m wondering if this could be a limitation of Podman.

Has anyone encountered similar issues or have suggestions on how to get the missing metricsets working?

Thanks in advance!