# High CPU usage: undertand events / traffic in discover view

**URL:** <https://discuss.elastic.co/t/high-cpu-usage-undertand-events-traffic-in-discover-view/376074>\
**Category:** Elasticsearch\
**Created:** [March 18, 2025, 1:56pm UTC](https://discuss.elastic.co/t/high-cpu-usage-undertand-events-traffic-in-discover-view/376074 "2025-03-18T13:56:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gerardo\_Zenobi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gerardo_zenobi/32/106790_2.png) [@Gerardo\_Zenobi](https://discuss.elastic.co/u/Gerardo_Zenobi)\
**Post date:** [March 18, 2025, 1:56pm UTC](https://discuss.elastic.co/t/high-cpu-usage-undertand-events-traffic-in-discover-view/376074/1 "2025-03-18T13:56:18Z")

</div>

Hello there,

I am trying to understand why my cluster is currently being overloaded (high cpu, enterprise search instances rebooting)

I stumbled upon the Discover view `/app/discover` view in Kibana:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/1/01483567f73f2de859b47275352d7f1e027691ac.png)

Our problems started exactly where we see an increase of logs / events.

I wanted to understand what do these different event datasets mean and why aren't they correlated (e.g. an app search api call would't trigger both events? ) :

- `app-search-analytics `
- `api`

Any other information on how to use this view to diagnose performance issues would be much appreciated.

Kind regards