Hi -
For your review & entertainment, pcpfans.git fche/pmmgr contains
code&qa for automagic logging of each container running on a host.
(Thence pmwebd and other tools can display/consume the data.)
commit 860e8db73916514a5aa6efd198d83f39696a65de
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Tue Mar 31 21:15:23 2015 -0400
pmmgr: subtarget-containers qa/668
A relatively short (60-second) test that fires up a pmmgr only in
order to attach pmloggers to a few *real live* docker containers.
(That means the qa-invoking user probably needs to be in group
'docker'; something checked by the qa script.) The docker container
being used is a tiny "busybox sleep XX" kind, so there should be
only minimal disk/network consumption.
The tests do not assert anything about the contents of the pcp
archives resulting from the per-container attachment. In my tests,
they got apprx. zero actual content, other than proper pmcd.hostname.
There ought to be a pmlogconf ditty for the container's own cgroup
stats, and disk/network stuff should eventually be correct.
commit 6147c9a71c2e34583104682eb0604ddc89ad132c
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Tue Mar 31 18:35:23 2015 -0400
pmmgr: subtarget-containers support
Add support for a config option "subtarget-containers", which
implicitly forks further pmlogger (but not pmie: PR1105) instances for
all running containers on an identified target host. The host's
host-id string gets a "--CONTAINER" code attached, and the connection
hostspec gets a "container=XXXXX" appended with a ? or & suffix-prefix.
|