From: "J. Bruce Fields" <bfields@fieldses.org>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsv4 monitoring tool
Date: Fri, 5 Apr 2013 08:58:33 -0400 [thread overview]
Message-ID: <20130405125833.GA1194@fieldses.org> (raw)
In-Reply-To: <20130405124822.GB25618@ics.muni.cz>
On Fri, Apr 05, 2013 at 02:48:22PM +0200, Lukas Hejtmanek wrote:
> Hello,
>
> On Mon, Oct 15, 2012 at 01:43:05PM -0400, J. Bruce Fields wrote:
> > > is there any NFSv4 monitoring tool, that can be run on NFSv4 server (running
> > > NFSv4.0 + GSS) and that reports statistics per connected client? I would like
> > > to see amount of transfered data for each client, latency of RPC calls, rate
> > > of requests.
> > >
> > > nfsstat on server does not distinguish individual clients.
> > > nfswatch does not support NFSv4
> > >
> > > I didn't find anything else. Do I need to create the tool by myself or is
> > > there free of paid tool thad does the job?
> >
> > We don't gather such statistics, unfortunately. I agree that it would
> > be useful, and would be happy to talk about possible implementations
>
> so we decided to implement this using systemtap tool and it works ok. But if
> NFS server could provide statistics by itself, it would be far better.
Sure. If you have a detailed description of the statistics that you're
gathering (and/or the systemtap scripts), that could help make sure we
capture what you need.
--b.
next prev parent reply other threads:[~2013-04-05 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 16:38 nfsv4 monitoring tool Lukas Hejtmanek
2012-10-15 17:43 ` J. Bruce Fields
2013-04-05 12:48 ` Lukas Hejtmanek
2013-04-05 12:58 ` J. Bruce Fields [this message]
2013-04-05 13:11 ` Lukas Hejtmanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130405125833.GA1194@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox