# Metricbeat reporting incorrect system.diskio.iostat.queue.avg\_size values

**URL:** <https://discuss.elastic.co/t/metricbeat-reporting-incorrect-system-diskio-iostat-queue-avg-size-values/242107>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [July 21, 2020, 10:27pm UTC](https://discuss.elastic.co/t/metricbeat-reporting-incorrect-system-diskio-iostat-queue-avg-size-values/242107 "2020-07-21T22:27:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mferreira22](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@mferreira22](https://discuss.elastic.co/u/mferreira22)\
**Post date:** [July 21, 2020, 10:27pm UTC](https://discuss.elastic.co/t/metricbeat-reporting-incorrect-system-diskio-iostat-queue-avg-size-values/242107/1 "2020-07-21T22:27:14Z")

</div>

I'm using Elastic's machine learning to detect anomalies in system usage data, one of the fields being **system.diskio.iostat.queue.avg\_size**. The data we are receiving occasionally reports anomalies in the disk IO average queue size that are incorrect and not possible.

As an example a particular server reports a typical value of 0.902 for this field but the actual value for the anomaly was 2,285,852,514,112.815.

This same anomaly has occurred across other systems, another one reporting a typical value of 0.684 and actual value of 1,091,778,685,151.05.

Is this an issue in how metricbeat is collecting system.diskio.iostat.queue.avg\_size data? How can this issue be fixed?

---

<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:** [August 19, 2020, 12:27am UTC](https://discuss.elastic.co/t/metricbeat-reporting-incorrect-system-diskio-iostat-queue-avg-size-values/242107/2 "2020-08-19T00:27:25Z")

</div>

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