pcp
[Top] [All Lists]

pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30 (+1000))
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 18 Apr 2013 18:01:44 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <454576207.2492751.1366239512859.JavaMail.root@xxxxxxxxxx>
References: <454576207.2492751.1366239512859.JavaMail.root@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: EptDO8bjlk3dhlgQBlsI7gO87Gn4dnPvjTcE
Thread-topic: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30 (+1000)

----- Original Message -----
> ...
> 11. Simplify default setup [Mark]
> Topic of making a default install simpler to setup for new users was
> broached.  Came up for Mark in wider discussions with other Red Hat
> customer support people, and pointing to the other tools like sar,
> collectl, etc which are basically "chkconfig on && service start" to
> get useful results.  With PCP we are not providing generally useful
> default setups today, which is just plain silly.
> 
> Ken points out that of everything discussed today, this one's by far
> the easiest and should be a no-brainer - if someone could propose a
> more useful set of metrics for /etc/pcp/pmlogger/config.default, it
> could happen immediately.  ...

Thinking further on this - is there any compelling reason not to make
config.default pmlogconf(1)-generated?  It'd be good to dog-food that
tool a bit more.  Its default-generated set, at least on my box with
quite a few PMDAs, looks fairly plausible.  That way we're providing
a mechanism for extending config.default as PMDAs are added, as well.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>