Hi there Henry,
(CC'ing the PCP list in case others come across this phenomenon too)
----- Original Message -----
> Hey Nathan,
>
> Thanks for the quick response!
>
> I was able to install the new code, and get data from those 3 new metrics.
>
> However the cgroup.memory.limit looks weird to me, i dont think this is in
> bit or bytes since it would be too large.
Thanks for trying it out! These values are sourced from the kernel via the
cgroup pseudo-filesystem, and we pass back (unmodified) the contents of the
statistics files for each cgroup.
You should be able to find these files and check what limits/usage the kernel
is applying. For cgroups that are used in Docker containers, you should see
things like:
$ cat
/sys/fs/cgroup/memory/system.slice/docker-c4f1a5c72ee11e819c1560b6a3be752d3dd6486f84df8322647ad96a184f1f4d.scope/memory.max_usage_in_bytes
14336000
$ cat
/sys/fs/cgroup/memory/system.slice/docker-c4f1a5c72ee11e819c1560b6a3be752d3dd6486f84df8322647ad96a184f1f4d.scope/memory.usage_in_bytes
528384
$ docker ps | grep c4f1a5c72ee
c4f1a5c72ee1 fedora:20 "/bin/bash" 18 hours ago
Up 18 hours jovial_galileo
$ pminfo --fetch --container=jovial_galileo cgroup.memory.usage
cgroup.memory.usage
inst [0 or
"/system.slice/docker-c4f1a5c72ee11e819c1560b6a3be752d3dd6486f84df8322647ad96a184f1f4d.scope"]
value 528384
cheers.
--
Nathan
|