| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Calculated/derived metrics? |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Fri, 08 May 2015 08:45:42 +1000 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <y0mwq0kf7mm.fsf@xxxxxxxx> |
| 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> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
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). I think the scenario is like this ... ---+-------------------------------+------ >time | | start_time uptime 0 100 170 200 >write_bytes and Marko wants 200/(uptime-start_time) at time "uptime" |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] build failure on fc20 [fixed], Ken McDonell |
|---|---|
| Next by Date: | Re: [pcp] install failing on openSUSE 13.1, Lukas Berk |
| Previous by Thread: | Re: Calculated/derived metrics?, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] Calculated/derived metrics?, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |