Bandwidth Speed Alerts?

Posted June 7, 2019 1.5k views
MonitoringUbuntu 18.04

Hello, I have a Droplet 48 GB Memory / 50 GB Disk / SFO2 running for my production site, I configured alerts with default values for CPU, Memory, Disk and also Bandwidth Speed (above 70.00 Mbps for 5 minutes). I received a few alerts saying that, for example “Network Transmit Bytes for droplet xxxx is currently at 441.67 Mbps, above setting of 70.00 Mbps… etc”. I was wondering: what does this metric really mean and should I be worried about those “peaks”? and, why I’m receiving and email alert when according to the Monitoring Tab, no alerts have been triggered and according to the graphs, the peaks are way below the 70.00 Mbps mark?

Alert Policies
Name Last Alert

CPU is running high . Never
CPU is above 70% for 10 min

Bandwidth — Outbound is running high Never
Bandwidth — Outbound is above 70Mbps for 5 min

Bandwidth — Inbound is running high
Bandwidth — Inbound is above 71Mbps for 5 min Never

Disk — Read is running high Never
Disk — Read is above 75MB/s for 5 min

Memory Utilization is running high . Never
Memory Utilization is above 70% for 5 min

I really hope this makes sense and someone could send me a clue :)

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
3 answers

I don’t have an answer, but I’m having a similar issue. The network bandwidth alerts are being triggered, but graphs show nothing. I can only assume it’s a bug, but I’m going to open a support request.

Getting the same ones here too, eventhough I haven’t even set up this kind of alert.
I suspect something buggy is going on at DO’s side.
(also opened a support ticket. I’ll update when I know more)

I just saw a message on DO’s dashboard:
Issues with Monitoring Alerts
Our engineering team has implemented a fix to resolve an issue with the Monitoring service and is monitoring the situation. ....

it looks that there is indeed a bug, thanks to both for the help :)