# How to read Metricbeat iowait time

**URL:** <https://discuss.elastic.co/t/how-to-read-metricbeat-iowait-time/155311>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 4, 2018, 6:32pm UTC](https://discuss.elastic.co/t/how-to-read-metricbeat-iowait-time/155311 "2018-11-04T18:32:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![grantcurell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grantcurell/32/23813_2.png) [@grantcurell](https://discuss.elastic.co/u/grantcurell)\
**Post date:** [November 4, 2018, 6:32pm UTC](https://discuss.elastic.co/t/how-to-read-metricbeat-iowait-time/155311/1 "2018-11-04T18:32:49Z")

</div>

![iowait](https://us1.discourse-cdn.com/elastic/original/3X/0/e/0efd4be6d8c0b929d736342bddd45e10224e5c2e.png)

I'm diagnosing some performance issues with a high speed security sensor I'm running. I strongly suggest disk I/O is my culprit. Metricbeat's has really helped me get insight on my stack's performance, but I'm not actually sure how to interpret the iowait field. See attached screenshot - what is that telling me?

Let me know if my Google-foo has failed me. If there's a resource that explains all this I'm happy to go read.

---

<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:** [December 2, 2018, 6:32pm UTC](https://discuss.elastic.co/t/how-to-read-metricbeat-iowait-time/155311/2 "2018-12-02T18:32:55Z")

</div>

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