Question
My Droplet stopped reporting CPU/memory/bandwidth usage to DO for 20+ minutes, is that normal?
- Posted on March 16, 2015
- DigitalOceanGetting StartedLoggingNetworkingUbuntu
Asked by Jason Johnson
I’m a VPS newbie running a LEMP stack with very low traffic. I’m curious if this is a normal glitch with DO’s graph page, or where I can look at maybe a log file to understand what (if anything) happened.
Looking at the graph for my droplet I see the CPU/memory/bandwidth usage is reported each minute, but there was a break for about 21 minutes tonight where there was no reporting at all for CPU or memory and only 1 report for bandwidth usage (0/0). At the end of this blank period there was a spike of outgoing bandwidth higher than anything else today. My VPS usually averages around 0.01 Mbps outgoing but this spike was 0.54Mbps just for that one poll and then went back to normal.
I thought maybe it was DOs automated backup, but that has not happened yet.
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!
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.
There are two reasons that your droplet’s graphs may show a gap like this:
1.) The droplet was powered off or unresponsive. If this is the case there would be other symptoms and the graphs would likely be the least of the problems.
2.) There was an issue on our end between the hypervisor and the graphs system. In this case there is no reason to believe there is any issue with your droplet and it should not be a cause for concern.
If there is no evidence in your log files and you didn’t experience any other problems with your droplet I would not be concerned about this.