Does the monitoring agent poll for metrics, or does it look at differences in performance counters over time?

I noticed recently that a batch job I’m running every 3h has far lower reported Disk I/O than is actually occurring (0.3 B/s rather than 30KB/s over a 20 minute window).

Most of the disk activity is concentrated in a small subset of that 20 minute window, so plausibly the monitoring agent is polling and recording the small amount of changes to file metadata and whatnot while completely missing the bulk of the data being written (as opposed to recording total changes since the last time the monitoring agent examined the disk).

Does that explanation make sense? Does the monitoring agent poll for current throughput, or is there something else going on?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there @hansvm,

I tried to reproduce this at my end but it seems to be working as expected.

I ran an I/O heavy operation while having iotop running and then I checked the graphs which represented the value accordingly:

Disk I/O DigitalOcean

However, if you believe that the data that you are seeing is way off the actual I/O, you could submit a GitHub issue here:

Hope that this helps! Regards, Bobby