Docker container memory consumption shows 293 billion percent

We have monitoring docker container with few Linux servers where the memory consumption shows as 293 billion percent, we have investigated with SolarWinds customer portal with this, and they state it is a bug. Also confirmed that the alert is doing its job as expected. Did anyone come across this scenario with the docker container. if yes, what will be the resolution for this issue.

Find more posts tagged with

Accepted answers

All comments

Seashore

I had a windows disk, volume, that reported to be several hundred of terabyte in size. Instead of a couple of hundred GB.
Was a issue with the device then. Reboot of the monitored server helped then

Sruth

Even we have rebooted the server, but no use,still the issue persists.

martin.john8880

We encountered the same issue with a Docker container showing 293 billion percent memory usage on Linux servers. SolarWinds support confirmed it's a known UI bug, and the alerting system is functioning correctly. A practical workaround is to apply filters or adjust thresholds to ignore the false readings. Also, if you're checking your NOL card Balance, be sure to use official and trusted sources for accurate results.

Sruth

@martin.john8880 Could you please provide the specific threshold values or filter settings you used to ignore the false memory usage readings? That would be really helpful.

quiazine

It’s a SolarWinds UI bug—the “293 billion% memory” reading is false. Alerts are working fine. Fix: adjust filters or thresholds to ignore it. For accurate info like NOL card balances, always use official sources. Quickymagazine also covers tips on monitoring tools and tech updates.

Kamalianoir

I’ve come across this behavior before it’s a known issue with how SolarWinds interprets Docker group metrics. The “293 billion percent” reading occurs when memory limits aren’t correctly parsed from the container stats. The best approach is to ensure your SolarWinds agent and platform are updated to the latest version or hotfix, as this bug has been addressed in recent builds. You can also cross-check memory usage directly using docker stats to confirm the actual values.