# How to calculate packebeat's Events Rate (/s) AND CPU Utilization (%)

**URL:** <https://discuss.elastic.co/t/how-to-calculate-packebeats-events-rate-s-and-cpu-utilization/186022>\
**Category:** Beats\
**Created:** [June 17, 2019, 8:59am UTC](https://discuss.elastic.co/t/how-to-calculate-packebeats-events-rate-s-and-cpu-utilization/186022 "2019-06-17T08:59:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lion00](https://avatars.discourse-cdn.com/v4/letter/l/3ec8ea/32.png) [@lion00](https://discuss.elastic.co/u/lion00)\
**Post date:** [June 17, 2019, 8:59am UTC](https://discuss.elastic.co/t/how-to-calculate-packebeats-events-rate-s-and-cpu-utilization/186022/1 "2019-06-17T08:59:45Z")

</div>

How to calculate packebeat's Events Rate (/s) AND CPU Utilization (%), I get data from monitoring-beats-\* . like this  
cpu":{"total":{"ticks":245888430,"time":{"ms":245888438},"value":2.4588843e+08},"user":{"ticks":197612870,"time":{"ms":197612871}},"system":{"time":{"ms":48275567},"ticks":48275560}}}

and  
libbeat":{"outputs":{"kafka":{"bytes\_write":158900659565,"bytes\_read":1215523855}},"pipeline":{"events":{"failed":49398,"dropped":0,"retry":281,"active":298,"total":248754897,"filtered":0,"published":248705499},"queue":{"acked":248705201},"clients":1},"config":{"reloads":0,"module":{"starts":0,"stops":0,"running":0}},"output":{"read":{"bytes":0,"errors":0},"type":"kafka","events":{"total":248705201,"acked":248705201,"failed":0,"dropped":0,"duplicates":0,"active":0,"batches":1130917}  
AND how can i calculate the CPU usage and Events Rate ?

---

<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 15, 2019, 10:59am UTC](https://discuss.elastic.co/t/how-to-calculate-packebeats-events-rate-s-and-cpu-utilization/186022/2 "2019-07-15T10:59:49Z")

</div>

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