I, too, am puzzled by the CRIT (730%) memory. It is only a single VM running HAPROXY on Debian Buster. It idles and uses virtually no resources at all and no matter how much RAM/SWAP I throw on it, the error never goes away.
I have dozens of VMs in the cluster and only one is throwing this puzzling CRIT.
Perhaps some of us are misreading the numbers below, but there is just no way I can make them add up to 730% committed.
If you have a suggestion of what I might adjust in the parameters, I’d love some input.
Total virtual memory: 2.92% - 119.43 MB of 4.00 GB, Committed: 730% - 29.23 GB of 4.00 GB virtual memory (warn/crit at 100.00%/150.00% used)**CRIT**, 8 additional details available
Details Total virtual memory: 2.92% - 119.43 MB of 4.00 GB
Committed: 730% - 29.23 GB of 4.00 GB virtual memory (warn/crit at 100.00%/150.00% used)**CRIT**
RAM: 2.69% - 55.13 MB of 2.00 GB
Swap: 3.14% - 64.30 MB of 2.00 GB
Commit Limit: -391.0% - -15.67 GB of 4.00 GB virtual memory
Shared memory: 3.43% - 70.27 MB of 2.00 GB RAM
Page tables: 3.96% - 81.07 MB of 2.00 GB RAM
Disk Writeback: 0% - 0.00 B of 2.00 GB RAM
RAM available: 97.31% free - 1.95 GB of 2.00 GB
Hardware Corrupted: 0% - 0.00 B of 2.00 GB RAM
This may not be OP’s exact situation, but it may be related.