pcp
[Top] [All Lists]

Re: [pcp] pcp updates - libpcp_import & PCP::LogImport

To: kenj@xxxxxxxxxxxxxxxx, Mark Goodwin <goodwinos@xxxxxxxxx>
Subject: Re: [pcp] pcp updates - libpcp_import & PCP::LogImport
From: nathans@xxxxxxxxxx
Date: Tue, 27 Jul 2010 10:58:17 +1000 (EST)
Cc: pcp@xxxxxxxxxxx
In-reply-to: <954974121.1247021280192141845.JavaMail.root@xxxxxxxxxxxxxxxxxx>
Sender: nscott@xxxxxxxxxx
----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:

> On Mon, 2010-07-26 at 22:34 +1000, Mark Goodwin wrote:
> ...
> > ok, pcp-import it is. I'll pull in Ken's tree and do the packaging
> > work + version bumps in dev to make this happen, and ..
> 
> Thanks Mark.
> 
> > ...
> > well yes, but in those cases they've moved into their own tree,
> > which is quite a bit more dramatic than just sub-packaging.
> > We need to avoid trees breeding like rabbits too - I'd really
> > rather that stuff came back into the pcp tree eventually.
> 
> +1 from me if this is feasible

I wouldn't be overly happy with infiniband coming back into pcp,
it was moved out for good reason IMO (external libs, headers and
added configure.in complexity).  Maybe cluster pmda, if it had a
brain transplant & became generic.

> > ps: /me is currently bombarded with iostat data - I can see
> iostat2pcp
> > happening before too long :)
> 
> Good luck here ... there appear to be a million option combinations
> possible (and hence ascii output formats), no binary data format,
> plus
> all the host-specific device naming, and (the real killer) iostat
> never
> reports the time of day nor the sample interval ... if you get this

Looks like -t option (at least to sysstat's iostat) will print the
timestamp for each sample.  And it appears the S_TIME_FORMAT env
variable set to "ISO" will give timestamp with timezone info.

cheers.

-- 
Nathan

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