# Metricbeat on Windows isn't aware of processor groups

**URL:** <https://discuss.elastic.co/t/metricbeat-on-windows-isnt-aware-of-processor-groups/221106>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 26, 2020, 8:11pm UTC](https://discuss.elastic.co/t/metricbeat-on-windows-isnt-aware-of-processor-groups/221106 "2020-02-26T20:11:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dannygoulder](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dannygoulder/32/22259_2.png) [@dannygoulder](https://discuss.elastic.co/u/dannygoulder)\
**Post date:** [February 26, 2020, 8:11pm UTC](https://discuss.elastic.co/t/metricbeat-on-windows-isnt-aware-of-processor-groups/221106/1 "2020-02-26T20:11:57Z")

</div>

On a Windows 2008R2 or 7 system (or later) with \>64 and \<=128 logical CPUs, Metricbeat only sees half the CPUs on the system. This is because of [Processor Groups](https://docs.microsoft.com/en-us/windows/win32/procthread/processor-groups).

Is there any plan for Metricbeat to support processor groups?

---

<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:** [March 25, 2020, 8:12pm UTC](https://discuss.elastic.co/t/metricbeat-on-windows-isnt-aware-of-processor-groups/221106/2 "2020-03-25T20:12:00Z")

</div>

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