pcp
[Top] [All Lists]

Re: [pcp] Calculated/derived metrics?

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: [pcp] Calculated/derived metrics?
From: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Fri, 08 May 2015 17:15:09 +0300
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <554BEB16.7030208@xxxxxxxxxxxxxxxx>
Organization: Red Hat
References: <5534C680.2020709@xxxxxxxxxx> <493537984.3276058.1429528962326.JavaMail.zimbra@xxxxxxxxxx> <5534EBA8.4030509@xxxxxxxxxx> <1644393599.3651017.1429563442835.JavaMail.zimbra@xxxxxxxxxx> <55364606.1000503@xxxxxxxxxx> <55472B40.7050800@xxxxxxxxxx> <5547DE11.5050800@xxxxxxxxxxxxxxxx> <5549E4CD.5000408@xxxxxxxxxx> <554AFE4E.80000@xxxxxxxxxxxxxxxx> <y0mwq0kf7mm.fsf@xxxxxxxx> <554BEB16.7030208@xxxxxxxxxxxxxxxx>
Reply-to: myllynen@xxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
Hi,

On 2015-05-08 01:45, Ken McDonell wrote:
> On 08/05/15 06:35, Frank Ch. Eigler wrote:
>> ...
>> Is the rate() derived-metrics function applicable here?
> 
> If I understand Marko's requirement he'd like to get something close to
> the I/O rate of the process over its life, rather than over the last
> time period (hotproc.io.write_bytes by itself will give you the latter,
> as will rate(hotproc.io.write_bytes) in a derived metric).

yes, I think there are certainly use cases for both, in this particular
case I was thinking checking e.g. with pmval or pmdumptext "hot"
processes' I/O activity for an application which does its I/O in bursts,
with rate() most often the result would be zero but with value() it'd
give instantly some sort of general idea what app has been up to
I/O-wise (so it'd be a perfect match for this derived convenience metric).

Thanks,

-- 
Marko Myllynen

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