| To: | myllynen@xxxxxxxxxx, Paul Evans <pevans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] NFS Server pmda |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Wed, 4 Feb 2015 04:43:11 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <54D1CD57.80908@xxxxxxxxxx> |
| References: | <54CFAF63.1000200@xxxxxxxxxx> <2063280794.5937221.1422915037777.JavaMail.zimbra@xxxxxxxxxx> <54D0E5A5.6040000@xxxxxxxxxx> <54D1CD57.80908@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | R07C8kHpuXbI3Y8VxLF3QXJJ1UG8oA== |
| Thread-topic: | NFS Server pmda |
Hi guys, ----- Original Message ----- > Hi, > > On 2015-02-03 17:13, Paul Evans wrote: > > On 02/02/15 22:10, Nathan Scott wrote: > >> At first glance there would appear to be overlap with metrics from the > >> Linux kernel PMDA - see the nfs.*, nfs3.*, nfs4.* and rpc.* metrics - > >> are there some additional metrics added here that don't exist there? > > Err, look like I missed that the nfs.*.reqs metrics had the different > > request types as instances. Pretty much everything that was to be > > added with nfsserver pmdas is already covered by the existing linux > > kernel pmda. > > yes, you're not the first one missing the fact, perhaps we should add a > quick note somewhere about this? *nod* - any ideas where it might go, that would be seen by someone going down this path? Maybe the issue is the existing metrics names not being expressive enough? cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] NFS Server pmda, Marko Myllynen |
|---|---|
| Next by Date: | Re: [pcp] NFS Server pmda, Marko Myllynen |
| Previous by Thread: | Re: [pcp] NFS Server pmda, Marko Myllynen |
| Next by Thread: | Re: [pcp] NFS Server pmda, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |