| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] hinv.* |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 28 Oct 2014 01:48:33 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <544F2DD5.40108@xxxxxxxxxxxxxxxx> |
| References: | <20141021222355.GC6656@xxxxxxxxxxxxxxx> <573592010.74725901.1413999659304.JavaMail.zimbra@xxxxxxxxxx> <54483934.4060802@xxxxxxxxxx> <20141023072636.GB6158@xxxxxxxxxxxxxxx> <1558759660.1356853.1414474824972.JavaMail.zimbra@xxxxxxxxxx> <544F2DD5.40108@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | 2CW8i9UdgqigTocQp7wlhjjRyQirWA== |
| Thread-topic: | hinv.* |
----- Original Message ----- > 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. > Ah, yes, that'll do the trick - thanks Ken. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] hinv.*, Mark Goodwin |
|---|---|
| Next by Date: | Re: [pcp] pcp updates: merges (mgoodwin, fche, kenj, self), qa, Ken McDonell |
| Previous by Thread: | Re: [pcp] hinv.*, Ken McDonell |
| Next by Thread: | Re: [pcp] hinv.*, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |