# Metricbeat doesn't recognize the process

**URL:** <https://discuss.elastic.co/t/metricbeat-doesnt-recognize-the-process/263176>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 3, 2021, 10:53pm UTC](https://discuss.elastic.co/t/metricbeat-doesnt-recognize-the-process/263176 "2021-02-03T22:53:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [February 13, 2021, 1:38am UTC](https://discuss.elastic.co/t/metricbeat-doesnt-recognize-the-process/263176/4 "2021-02-13T01:38:26Z")

</div>

Hi @xyz2  
You can do both... there are probably a couple ways but here is a way you just set up to separate process collectors. First one does top N, second looks for specific processes.  
Give it a try ... let us know

```
- module: system
  period: 10s
  metricsets: ['process']
  process.include_top_n:
    by_cpu: 5 # include top 5 processes by CPU
    by_memory: 5 # include top 5 processes by memory

- module: system
  period: 10s
  metricsets: ['process']
  processes: ['^sysmon*']
```

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-doesnt-recognize-the-process/263176)._