pcp
[Top] [All Lists]

Re: A few questions

To: Alan Bailey <abailey@xxxxxxxxxxxxx>
Subject: Re: A few questions
From: Max Matveev <makc@xxxxxxx>
Date: Mon, 15 Jan 2001 10:40:41 +1100 (EST)
Cc: pcp@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.10.10101101421420.28431-100000@osage.ncsa.uiuc.edu>
References: <Pine.LNX.4.10.10101101032570.25987-100000@osage.ncsa.uiuc.edu> <Pine.LNX.4.10.10101101421420.28431-100000@osage.ncsa.uiuc.edu>
Sender: owner-pcp@xxxxxxxxxxx
>>>>> "AB" == Alan Bailey <abailey@xxxxxxxxxxxxx> writes:

AB> A few simple questions...
AB> - I'm using the following command:

AB> > pmafm Latest pmdumplog -S "@whatever"

AB> This is all fine and good.  But say I just want a single metric.  This
AB> doesn't work:

AB> > pmafm Latest pmdumplog -S "@whatever" mem.freemem
AB> pmdumplog: Cannot open archive "mem.freemem": No such file or directory

AB> Obviously, this is because there is no archive on the command line, and
AB> mem.freemem is thought to be the archive.  Is there a way around this, or
AB> is this just the way it is?

That's because pmdumlog is not the best tool for this job. Partially
becuase it's command line options are not the same as "the rest", i.e
it doesn't use -a to specify archives. Try pmval -S "@whatever" with
'repeat'

i.e

pmafm Latest repeat pmval -S "@sometime" mem.freemem

AB> - Is there a way to round the time values in the archives to, say, every
AB> five minutes, so that 13:42:23.045 would become 13:40?  I doubt this,
AB> because I know the code for any arbitrary rounding time would be
AB> nontrivial, and this isn't that necessary.

You're right here. You can achieve similar effect with some extra -S
and -t options to be passed to your pmlogger. It still wouldn't
guaranty exact round time, but it will be close.

AB> - Is pminfo the suggested way to get a single value from an archive at a
AB> certain time, and pmdumplog the suggested way to get a range of time
AB> values?

Pretty much so. You can use pmval but it's more heavy-weight compared
to pminfo and pmprobe doesn't do times, it only does one metric at the
top of the archive.

max

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