>- is there a way to "link" the cgroup id to the mesos task id? The cgroup id you saw is the ContainerId actually. You could get the mapping relations from querying the state endpoint of Mesos agent.
>In mesos, this information is set to /, so all my process are shown in the / cgroup. May you mind provide more details about this? As I know, all the mesos containers should under `Flags::cgroups_root` which default value is "mesos". In additionally, do you ever try the `/metrics/snapshot` endpoints of Mesos Master and Mesos Agent, which provide some useful messages could used to monitor as well. On Fri, Jul 29, 2016 at 10:07 PM, [email protected] < [email protected]> wrote: > > > > Hello. > > > I'm trying to find a solution to monitor the real usage of my mesos tasks. > I don't use docker at all, but I gave a look to cadvisor. > > > Unfortunatly, cadvisor uses ps and the device information to determine the > cgroup ownership of a process. In mesos, this information is set to /, so > all my process are shown in the / cgroup. > > > I can monitor the usage of the cgroups however, but I have no clue of > which process are inside, and the cgroup name is not related to the taskid > in mesos. > > > So, 3 questions: > > - is anybody managed to use cadvisor (with ou without mesos) for cgroups? > > - is there a "better" solution ? > > - is there a way to "link" the cgroup id to the mesos task id? > > > Thanks for any clue. > > > And a good sysadmin appreciation day! > > > Aurélien. > > -- Best Regards, Haosdent Huang
