| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] hinv.* |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 28 Oct 2014 16:47:01 +1100 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1558759660.1356853.1414474824972.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <20141021222355.GC6656@xxxxxxxxxxxxxxx> <573592010.74725901.1413999659304.JavaMail.zimbra@xxxxxxxxxx> <54483934.4060802@xxxxxxxxxx> <20141023072636.GB6158@xxxxxxxxxxxxxxx> <1558759660.1356853.1414474824972.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
On 28/10/14 16:40, Nathan Scott wrote: Yeah, hmmm, thats a bit awkward - I don't really want us to have to explicitly list each hinv metric in the logging configs. Not sure what else we can do though. You can log hinv once (as we do today), _and_ add another clause to log hinv.something and hinv.otherthing with the default logging frequency. I think that is manageable, unless I'm misunderstanding the issue. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] hinv.*, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] hinv.*, Mark Goodwin |
| Previous by Thread: | Re: [pcp] hinv.*, Nathan Scott |
| Next by Thread: | Re: [pcp] hinv.*, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |