# \[Metricbeat\] Process modules produces high load / cpu usage

**URL:** <https://discuss.elastic.co/t/metricbeat-process-modules-produces-high-load-cpu-usage/294923>\
**Category:** Beats\
**Tags:** docker, metricbeat\
**Created:** [January 20, 2022, 9:58am UTC](https://discuss.elastic.co/t/metricbeat-process-modules-produces-high-load-cpu-usage/294923 "2022-01-20T09:58:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adsr](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@adsr](https://discuss.elastic.co/u/adsr)\
**Post date:** [January 20, 2022, 9:58am UTC](https://discuss.elastic.co/t/metricbeat-process-modules-produces-high-load-cpu-usage/294923/1 "2022-01-20T09:58:54Z")

</div>

Hi,

after upgrading metricbeat from 7.11.2 to 7.16.3 I notice very high load/cpu usage for the metricbeat process.  
I narrowed it down to the `process` module in combination with a `python` process.  
Furthermore I tried several versions of which at least 7.16.x, 7.15.x and 7.14.x are affected

- Version: 7.16.3 (+7.15.x, +7.14.x)
- Operating System: CentOS 7

Config:

```auto
#========================== Modules configuration ============================

metricbeat.modules:
  - module: system
    metricsets:
      - cpu
      - core
      - load
      - memory
      - network
      - process
    ticks: False
    enabled: True
    period: 10s
    process.cgroups.enabled: True
    processes:
      - .*
  - module: system
    metricsets:
      - diskio
      - uptime
    enabled: True
    period: 60s
  - module: system
    metricsets:
      - filesystem
      - fsstat
    enabled: True
    period: 60s
    filesystem.ignore_types: []

  - module: docker
    metricsets:
      - cpu
      - memory
    enabled: True
    period: 10s
    hosts:
      - "unix:///var/run/docker.sock"
  - module: docker
    metricsets:
      - container
      - event
      - healthcheck
      - info
      - network
    enabled: True
    period: 60s
    hosts:
      - "unix:///var/run/docker.sock"

#================================ General =====================================

# The 'name' property refers to the host name
# This field is added as "host.name" to the event
name: my-host
fields:
  env: production
tags:
  - myhost
max_procs: 2

#============================== Processors ====================================

processors:
  - add_host_metadata:
      netinfo.enabled: true
      cache.ttl: 60m

#================================ Outputs =====================================

output.logstash:
  enabled: true
  hosts:
    - logstash:6033
  index: metricbeat
  compression_level: 3
  worker: 1
  loadbalance: true
  pipelining: 0
  slow_start: true

output.console:
  enabled: false
  pretty: true

#================================ Logging =====================================

logging.level: info
logging.selectors: []

logging.to_syslog: false
logging.to_files: true
logging.files:
  rotateeverybytes: 10485760 # = 10MB
  keepfiles: 7

```

Any input is highly appreciated!

Workarounds:

- downgrade to 7.13.4
- disable the process module

---

<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 17, 2022, 11:59am UTC](https://discuss.elastic.co/t/metricbeat-process-modules-produces-high-load-cpu-usage/294923/2 "2022-02-17T11:59:24Z")

</div>

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