| To: | William Staten <William_Staten@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Queston about pcp performance metrics filesys.used |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 9 Feb 2016 16:31:13 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <OF1B9DD255.E1F86B08-ON85257F54.004E7C3F-85257F54.005054A1@xxxxxxxxxxxxxxx> |
| References: | <OF1B9DD255.E1F86B08-ON85257F54.004E7C3F-85257F54.005054A1@xxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | w32X4ciQ2dnS7AmhlBrgX2ExRTy/cw== |
| Thread-topic: | Queston about pcp performance metrics filesys.used |
Hi William, ----- Original Message ----- > Good Morning. I wanted to know for the filesys metrics, was it a way to get > the name of the filesystem mounted or the full device mapper name to display > instead of just "/dev/dm-#". For example if I want to see the metric for > filesys.used for /home, instead of showing /dev/dm-7, could I get > rootvg-homelv to get displayed or /home to get displayed instead of > /dev/dm-7? The former (rootvg-homelv) is indirectly available via hinv.map.dmname but the latter (/home -> mount point) is not necessarily a one-to-one mapping with device, so gets more complicated. You might also find pmdamounts(1) of use for your situation, in recent PCP versions it exports all of the same metrics as filesys.* for a specified set of mount points. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Derived metric issues, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pcp2graphite improvement: send all metrics at once in pickled mode (#66), dbrolley |
| Previous by Thread: | Re: [pcp] Queston about pcp performance metrics filesys.used, Ken McDonell |
| Next by Thread: | Re: [pcp] Queston about pcp performance metrics filesys.used, William_Staten |
| Indexes: | [Date] [Thread] [Top] [All Lists] |