| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates: mem.util.available for kernels that don't export MemAvailable |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Sun, 6 Jul 2014 21:01:31 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <53B903E1.3000604@xxxxxxxxxx> |
| References: | <53B903E1.3000604@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | PN221kp/bO2/DvwT9r/OvwYw3+6q4Q== |
| Thread-topic: | pcp updates: mem.util.available for kernels that don't export MemAvailable |
Hi Mark, ----- Original Message ----- > [...] A new QA test is brewing > to check this and a new pmie rule with syslog alerts for production > environments might be warranted too. Sounds good. I've reverted 3c479d028 to give some minimal coverage until then - you might find either pmprobe with a derived metric to be a useful vehicle for doing that verification, or perhaps pmie. (I'm not a huge fan of $PCP_QA_ESTIMATE_MEMAVAILABLE, FWIW - seems a roundabout kind of way to check the value, the above two suggestions might be simpler? - *shrug* - your call of course). Would you recommend updating the pmchart "Overview" view to use this metric? (this metric will be automatically included in the logged set BTW, via src/pmlogconf/kernel/memory-linux - so nothing to do in that neck of the woods). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: QA test 828 has started failing, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pcp updates: mem.util.available for kernels that don't export MemAvailable, Mark Goodwin |
| Previous by Thread: | pcp updates: mem.util.available for kernels that don't export MemAvailable, Mark Goodwin |
| Next by Thread: | Re: [pcp] pcp updates: mem.util.available for kernels that don't export MemAvailable, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |