# Discrepancy between CPU usage shown in Kibana vs AWS cloud watch metrics

**URL:** <https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346>\
**Category:** Kibana\
**Created:** [December 9, 2021, 4:20pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346 "2021-12-09T16:20:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![taugusti](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@taugusti](https://discuss.elastic.co/u/taugusti)\
**Post date:** [December 9, 2021, 4:20pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/1 "2021-12-09T16:20:04Z")

</div>

I run Elasticsearch on EC2 instances launched in AWS. I use version 7.11.2. I've been load testing searches and I see CPU spikes up to 100% on data nodes when I look in Kibana. However, in AWS cloud watch I never see CPU spiked that much on any of the nodes, ever. What could possibly be the reason behind the discrepancy

---

<div class="post-metadata">

**Author:** ![majagrubic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majagrubic/32/74459_2.png) [@majagrubic](https://discuss.elastic.co/u/majagrubic)\
**Post date:** [December 9, 2021, 5:41pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/2 "2021-12-09T17:41:30Z")

</div>

How are you getting EC2 metrics into ES?

---

<div class="post-metadata">

**Author:** ![taugusti](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@taugusti](https://discuss.elastic.co/u/taugusti)\
**Post date:** [December 9, 2021, 10:49pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/3 "2021-12-09T22:49:33Z")

</div>

I'm usinng Kibana

---

<div class="post-metadata">

**Author:** ![majagrubic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majagrubic/32/74459_2.png) [@majagrubic](https://discuss.elastic.co/u/majagrubic)\
**Post date:** [December 10, 2021, 6:49am UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/4 "2021-12-10T06:49:23Z")

</div>

Kibana offers several integrations to get your metrics in an Elasticsearch cluster. Are you using Metricbeat, as offered under standard AWS integration?

---

<div class="post-metadata">

**Author:** ![taugusti](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@taugusti](https://discuss.elastic.co/u/taugusti)\
**Post date:** [December 10, 2021, 1:11pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/5 "2021-12-10T13:11:30Z")

</div>

I'm not using metricbeat. I'm using the standard monitoring that comes out of the box.  
Does it matter how kibana gets the values ? Whatever way, it should be same right ?

---

<div class="post-metadata">

**Author:** ![majagrubic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/majagrubic/32/74459_2.png) [@majagrubic](https://discuss.elastic.co/u/majagrubic)\
**Post date:** [December 10, 2021, 3:24pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/6 "2021-12-10T15:24:49Z")

</div>

Your question is very vague, so in order for us to help you, I'm trying to get as much information as I can. Could be an ingestion problem, could be an aggregation problem, could be a visualization problem (unlikely, but still).

---

<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:** [January 7, 2022, 3:25pm UTC](https://discuss.elastic.co/t/discrepancy-between-cpu-usage-shown-in-kibana-vs-aws-cloud-watch-metrics/291346/7 "2022-01-07T15:25:48Z")

</div>

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