# Getting aggregated view of 100% CPU across all dashboard views for windows server

**URL:** https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 20, 2018, 10:37am UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857 "2018-04-20T10:37:36Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![maheshm](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@maheshm](https://discuss.elastic.co/u/maheshm)
#### Post date: [April 20, 2018, 10:37am UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/1 "2018-04-20T10:37:36Z")

</div>

Hi,

We have been trying to achieve a breakdown of the active CPU% distributed between all the active process. Here's an example: If we have 8CPU, we see the total will be 800% and the active process consumption goes above 100% which is not ideal.

[Question about system.process.cpu.total.pct](https://discuss.elastic.co/t/question-about-system-process-cpu-total-pct/78926/5) Question about system.process.cpu.total.pct says that windows is a discrepancy where metricbeat is not accurate.

![image](https://us1.discourse-cdn.com/elastic/original/3X/a/1/a16f65bbec9f50a2a1d7b842907f83c5a28a7e01.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/e/deeb4288b1cfab1a26b7d33d5cefb93601a8bb75.jpg)

Please help/clarify if this can be sorted.

Thanks  
Mahesh

---

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [April 20, 2018, 1:55pm UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/2 "2018-04-20T13:55:22Z")

</div>

The post you linked to is kind of old. I believe that since then we made [some changes](https://github.com/elastic/beats/issues/4468). The [`system.process.cpu.total.norm.pct`](https://www.elastic.co/guide/en/beats/metricbeat/current/exported-fields-system.html#_literal_system_process_cpu_total_norm_pct_literal) value ranges on 0 to 100%. You should be able to verify that by look at the individual events in a non-aggregated view (Discover tab) and doing a Lucene query like `system.process.cpu.total.norm.pct:>=1`.

What version of Metricbeat is being used?

---

<div class="post-metadata">

### Author: ![maheshm](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@maheshm](https://discuss.elastic.co/u/maheshm)
#### Post date: [April 27, 2018, 4:28am UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/3 "2018-04-27T04:28:28Z")

</div>

Thanks AndreW. It is metricbeat 6.2.1 and still is going beyond 100%. Is there a possible way to put a calculation (system.cpu.total/no.of.cores) to get accurate values? Is system.cpu.total.pct should be considered for this? And, system.cpu.system.pct measure for?

---

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [April 27, 2018, 1:40pm UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/4 "2018-04-27T13:40:21Z")

</div>

I would consider it a bug if the normalized CPU metrics are going over 100%. Can you please open a bug report on [Github](https://github.com/elastic/beats/issues/new) for this issue and include a raw event in JSON form (you can grab that from Kibana's Discover page).

> [@maheshm](#):
>
> Is there a possible way to put a calculation (system.cpu.total/no.of.cores) to get accurate values? Is system.cpu.total.pct should be considered for this? And, system.cpu.system.pct measure for?

As a workaround, yes, it's definitely possible to do your own calculations. There is a `system.cpu.cores` metric which contains the total number of cores. With that value I think you should be able to do your own calculation.

You can do the calculation either at ingest time by using Logstash. Or you can add a [scripted field to Kibana](https://www.elastic.co/guide/en/kibana/current/scripted-fields.html).

This is a filter example in LS that shows how you can do a calculation. (I'm not sure these calculations are relevant -- I just copied it from somewhere to demonstrate how it can be done.)

```auto
filter {
  ruby {
    code => "
      event.set('[system][cpu][total][norm][pct]', 1 - (event.get('[system][cpu][idle][pct]') / event.get('[system][cpu][cores]') ))
      event.set('[system][cpu][total][pct]', event.get('[system][cpu][total][norm][pct]') * event.get('[system][cpu][cores]') )
    "   
  }
}

```

---

<div class="post-metadata">

### Author: ![maheshm](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@maheshm](https://discuss.elastic.co/u/maheshm)
#### Post date: [May 7, 2018, 9:22am UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/5 "2018-05-07T09:22:59Z")

</div>

Thanks Andrew, I see the normalized CPU is defined only for process by CPU. However, I wanted to understand if there is any defined normalized CPU for system/server?

![image](https://us1.discourse-cdn.com/elastic/original/3X/f/5/f58c0f264de0a23ff004a63b48ec6e822e02f130.png)

---

<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: [June 4, 2018, 9:23am UTC](https://discuss.elastic.co/t/getting-aggregated-view-of-100-cpu-across-all-dashboard-views-for-windows-server/128857/6 "2018-06-04T09:23:03Z")

</div>

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