| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Calculated/derived metrics? |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 05 May 2015 07:01:05 +1000 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <55472B40.7050800@xxxxxxxxxx> |
| 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> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 04/05/15 18:18, Marko Myllynen wrote: ... I think it would still be interesting to hear experiences around this, if calculated/derived metrics are needed in some cases, how to get them most efficiently? Marko, There is already a pretty complete derived metrics implementation.It uses a configuration file to define the expressions for the derived metrics and assign names to them, then the implementation sits in the data path so that all PMAPI calls for metadata or metric values are translated appropriately. Refer to pmRegisterDerived(3) for the expression syntax. PCPIntro(1) describes the environment variable $PCP_DERIVED_CONFIG that needs to be set to pathname to a file containing the definitions of the derived metrics in form needed by pmLoadDerivedConfig(3). If this does not address your needs I'd be keen to hear how and why. Cheers, Ken. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates - qa fixup, Ken McDonell |
|---|---|
| Next by Date: | Re: [pcp] proc PMDA problems, Nathan Scott |
| Previous by Thread: | Calculated/derived metrics?, Marko Myllynen |
| Next by Thread: | Re: [pcp] Calculated/derived metrics?, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |