# Slowness in Kibana and high CPU utilization usage

**URL:** <https://discuss.elastic.co/t/slowness-in-kibana-and-high-cpu-utilization-usage/352824>\
**Category:** Elasticsearch\
**Created:** [February 8, 2024, 7:04am UTC](https://discuss.elastic.co/t/slowness-in-kibana-and-high-cpu-utilization-usage/352824 "2024-02-08T07:04:28Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Seemant\_Bind](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seemant_bind/32/107045_2.png) [@Seemant\_Bind](https://discuss.elastic.co/u/Seemant_Bind)\
**Post date:** [February 8, 2024, 7:04am UTC](https://discuss.elastic.co/t/slowness-in-kibana-and-high-cpu-utilization-usage/352824/1 "2024-02-08T07:04:28Z")

</div>

Hi,

I am facing slowness in Kibana Production. Discover and dashboard is taking too much time to load and sometimes getting the error as shown in the first screenshot.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/b/6b8b808fe8b4a469d324030d5642424050e4d49a.png)

I checked the cluster status from the stack monitoring and found that one of my nodes had almost 100% CPU utilization throughout the day, I tried restarting the cluster but still it went back to 100% CPU utilization and can see still see the slowness.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/e/8e6fb8bcbf826f1f5a16eee24603b8e97e437fff.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/d/dd7a983ccbdf33ac6f0dd3b341b83d63c595c811.jpeg)

Then I checked the cluster log and found below:

```auto
[2024-02-07T09:01:24,958][ERROR][o.e.x.w.Watcher] [node-1] watch history could not be written [watch_id1_7a318241-b965-47d5-a80e-f4fe0d412739-2024-02-07T09:01:03.356624867Z], failure [java.lang.IllegalArgumentException: Limit of total fields [1000] has been exceeded]
[2024-02-07T09:02:04,055][ERROR][o.e.x.w.Watcher] [node-1] watch history could not be written [watch_id2__67cde037-f556-4a9f-a541-dc4df43bf787-2024-02-07T09:02:03.390800241Z], failure [java.lang.IllegalArgumentException: Limit of total fields [1000] has been exceeded]
[2024-02-07T09:02:04,103][ERROR][o.e.x.w.Watcher] [node-1] watch history could not be written [watch_id3__8cfb38f3-ef5d-43e4-92c2-41477d16af6e-2024-02-07T09:02:03.390800241Z], failure [java.lang.IllegalArgumentException: Limit of total fields [1000] has been exceeded]
[2024-02-07T09:02:04,420][ERROR][o.e.x.w.Watcher] [node-1] watch history could not be written [watch_id4__104ffd97-fc21-47f2-88ef-38656438b433-2024-02-07T09:02:03.390800241Z], failure [java.lang.IllegalArgumentException: Limit of total fields [1000] has been exceeded]

```

We currently have around 140 active watcher scripts running. Can you please guide us what exactly is causing the issue? Is there any correlation between the above watcher errors and slowness in Kibana/High CPU utilisation? Let me know if you need any additional information.  
Below is my ELK Stack Details -  
ELK Version: 7.11.1  
ES Node: 3  
Dedicated servers for Kibana and logstash  
Kibana Users: 154

---

_[View the full topic](https://discuss.elastic.co/t/slowness-in-kibana-and-high-cpu-utilization-usage/352824)._
