| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, myllynen@xxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Derived Metrics with rate() |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Sun, 28 Jun 2015 18:41:26 -0400 (EDT) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <00e801d0b124$8b825d60$a2871820$@internode.on.net> |
| References: | <558BAC86.2090005@xxxxxxxxxx> <00e801d0b124$8b825d60$a2871820$@internode.on.net> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | AQLV/j1Rhufu5wCc7WTSBIPH/EgvmgDHlmxbUVjIlXs= |
| Thread-topic: | Derived Metrics with rate() |
----- Original Message ----- > [...] > > My current thoughts are to extend $PCP_DERIVED_CONFIG to be a $PATH-style > list, and then if a directory appears in the list, all the files in that > directory will be processed as though they are derived metric specification > files. This is (a) backwards compatible, (b) optional, and (c) gives a > short-hard way of naming a bunch of derived metric files. > > I'd greatly appreciate feedback on this "library" of derived metrics > suggestion. > I like it - nice & simple too. I think it would also be good to promote the --derived pminfo option to be a standard option that all tools can easily access (via pmGetOptions) - I'm happy to hack on that bit if people tend to agree? cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] qa/1024 and disk partitions/docker indom issues, Nathan Scott |
|---|---|
| Next by Date: | Re: Solaris build notes, Nathan Scott |
| Previous by Thread: | RE: [pcp] Derived Metrics with rate(), Ken McDonell |
| Next by Thread: | Re: [pcp] Derived Metrics with rate(), Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |