What is likely to cause these gaps in monitoring metrics?

Posted November 28, 2020 523 views

Hi folks, I’ve been running a process on an ‘ubuntu-m-8vcpu-64gb’ machine with 200GB SSD, and ran into an issue when monitoring seems to drop and my process never finishes. I tried it twice (1st at 09:00, which failed at 11:30, and the 2nd at 14:30, which failed at 16:00), but I can’t determine if the machine is actually running out of resources. Is there any indication based on my screenshots below as to what might be happening for these gaps to occur?

Screenshot 1
Screenshot 2
Screenshot 3

If there’s any recommended process logging I could set/check then I’m all ears.


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.

Submit an Answer
2 answers

Hi there @amthomas,

I think that this could be caused by some really high workload on the Droplet so that the whole server gets unresponsive and the monitoring agent is unable to collect any data.

What I would usually do in this case is to put together a short script to note down the processes to a log file so that I could review them later on after the spike and try and figure out what exactly happened. Here is an example script that you could use:

Another approach rather than using a custom script is to use SAR/systat instead. The sar command allows you to capture the utilization of your resources like RAM, CPU, Disk I/O and etc.

Here is how to install and configure it on Ubuntu:

Hope that this helps!