Hi Frank,
On Tue, Apr 29, 2014 at 03:28:18PM -0400, Frank Ch. Eigler wrote:
> michele wrote:
> > [...]
> > I am in the process of adding support for PCP in sosreport[1]. [...]
> > /var/log/pcp, /var/lib/pcp/config, /etc/pcp,
> > /etc/pcp.conf, /etc/pcp.env, /etc/pcp.sh
>
> Note that /etc/pcp.conf is an input to .env / .sh; the latter are just
> non-adustable shell scripts. The variables set inside /etc/pcp.conf
> can redirect the location of many other bits. For example, instead of
> hardcoding the /var/log/pcp directory name, sosreport -might- consider
> getting the PCP_LOG_DIR value out of /etc/pcp.conf.
good idea, I did this[1] so customized cases will be covered.
> > [...] I'd imagine that extra carefulness needs to be taken for
> > /var/log/pcp in order to avoid collecting stuff (logger data?) that
> > is bigger than X unless explicitely asked for. I assume they can
> > grow moderately big, although I don't have any real-world data on
> > that.
>
> The bulk archives (*.[0-9]*, .meta, .index files) certainly grow big:
> 10-20 MB per day per host, kept by default for 14 days. It can blow
> up multiplicatively for longer-than-default or multiple-host
> logging. OTOH, the files are highly (90%+) compressible, and provide
> a good detailed performance overview of the host(s).
>
> Other files in there are small and valuable for diagnosing problems
> with pcp itself.
Ok. I've added an sensible default upper limit (100MB) and a user can
override via an option.
Thanks again and regards,
Michele
[1] https://github.com/mbaldessari/sosreport/blob/pcp-plugin/sos/plugins/pcp.py
--
Michele Baldessari <michele@xxxxxxxxxx>
C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D
|