We are running Debian as OpenVZ and LXC containers and running snmpwalk against an OpenVZ container you got correct values - running the same against an LXC containers you get wrong values.
We evaluated LXC about three years ago but it was not useable at all but we now finally have to move away from OpenVZ 6 and just testing with LXC again.
OpenVZ are also containers, therefore i thought it’s maybe a configuration thing to get LXC reporting the correct CPU values - and it’s only the CPU values we’ve discovered so far, don’t know how containers work in depth but seems they are different on this.
Thanks for mentioning netdata, installed it in a VM to take a quick look on it but it seems only to be a local host monitoring tool rather then a monitoring solution.
There are things which run inside the container and need to be monitored there, don’t know how a monitoring solution would combine things monitored outside on the host and inside a container and graph that up properly.
When CPU resources of LXC containers can only be monitored on the host it seems the only option is to move to KVM then as proper resource monitoring is a must.
Thanks,
cody