pcp
[Top] [All Lists]

Re: [pcp] pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 0

To: Mark Goodwin <goodwinos@xxxxxxxxx>
Subject: Re: [pcp] pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30 (+1000))
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri, 19 Apr 2013 00:23:29 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx, "Bryn M. Reeves" <bmr@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5170BE15.20409@xxxxxxxxx>
References: <454576207.2492751.1366239512859.JavaMail.root@xxxxxxxxxx> <2112139220.3147466.1366322504002.JavaMail.root@xxxxxxxxxx> <5170BE15.20409@xxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: ZlVOnw5uAz1e+0P5W5WOyNHJzHAOpA==
Thread-topic: pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30 (+1000))
Hi Mark,

----- Original Message -----
> ...
> 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

*nod*

> 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).

Good idea.  Rather than keeping two copies of the config files for
each tool, it'd be worthwhile moving the existing configuration
(find src -name pmlogger.config) into pmlogconf/tools and using it
as a starting point.  Will clean up /etc/pcp/pmlogger too without
all those in there - bonus.

> 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.

*nod* ... maybe add -r option to pmlogger in the control file too?

> 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 ...

Yes, sorry - I neglected to mention that in my writeup.  I think for
some people with just one or two systems (or desktops) it will help.
Alot of sysadmins prefer puppet/chef to manage systems now though, &
for them the GUI config tool option is less useful.

But if its a simple, easy-to-follow python script, for example, it'd
still be useful as a reference to people with more complex needs ...
so, go for it (PyQt for the win).

cheers.

--
Nathan

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