# Metricbeat CPU percent on Hyper-V Server

**URL:** <https://discuss.elastic.co/t/metricbeat-cpu-percent-on-hyper-v-server/275083>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [June 6, 2021, 8:50pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percent-on-hyper-v-server/275083 "2021-06-06T20:50:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![notrix](https://avatars.discourse-cdn.com/v4/letter/n/50afbb/32.png) [@notrix](https://discuss.elastic.co/u/notrix)\
**Post date:** [June 6, 2021, 8:50pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percent-on-hyper-v-server/275083/1 "2021-06-06T20:50:37Z")

</div>

hey all,

currently facing a problem with mericbeat on a Windows Server 2019 with Hyper-V role installed. This server is a pure virtualization server, hosting a lot of VMs.

Using metricbeat 7.13.1 and have the following config in my system.yml module:

```auto
module: system
period: 10s
cpu.metrics: ["normalized_percentages"]
metricsets:
   - cpu
   - memory

```

While the memory readings are consistent with what I'm seeing in taskmanager, the cpu metrics are completely off. I figured out, that the performance metrics don't "see" the CPU load created by all the virtual machines running on ther server ... so my CPU load is always around 1%. I tested with some heavy load on the server itself (running prime95) and the load goes up accordingly. Doing the same (running prime95 in a VM) doesn't increase the CPU load seen by metricbeat (but taskmanager shows it).  
Is there a way to fix that?

thanks!

---

<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:** [July 4, 2021, 10:50pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percent-on-hyper-v-server/275083/2 "2021-07-04T22:50:45Z")

</div>

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