On 04/19/2013 08:01 AM, Nathan Scott wrote:
----- 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.
make sense. I'll make a start on this approach, beginning with
spring cleaning the existing stuff; there are some very IRIXY
entries that should be just nuked (kernel/*-irix). And some that
need Linux porting (e.g. filesystem/xfs-io-irix). Others need
reviewing and I think we need a whole new group based on the
metrics required by various tools (pmclient, pmstat, sar, iostat,
vmstat, collectl / pmcollectl and so forth).
The resulting set of metrics (as a more-or-less configurable union)
should constitute a reasonable default logging config - allowing most
tools to replay archives, with enough extra scope for drill-down with
generic tools (pmchart esp.). We'll also need to measure daily data
volumes on variopus sized machines and adjust sampling rates so other
tools like sos-report wont balk, and also so the data collection
itself remains reasonably unintrusive on system resources.
In the meeting we also briefly discussed a "setup-pcp" tool (possibly
py/gui based) to manage services, configure logging (e.g. call out
to pmlogconf), manage PMDA enablement, security, etc., Any thoughts
on that? This kind of thing should help reduce the learning curve ...
-- Mark
|