Our NFS integration collects and sends inventory and metrics from your NFS service to our platform, where you can see disk usage data so that you can more easily find the source of any problems.
Read on to install the integration, and to see what data we collect.
Our integration is compatible with NFS version 3 or 4.
Before installing the integration, make sure that you meet the following requirements:
- Install the infrastructure agent, minimum version 1.5.40, on host (NFS client)
- Linux distribution compatible with the infrastructure agent
The NFS integration is already activated and installed by default. Therefore, there are no installation or activation requirements, as it works out of the box. See samples variables, and search for NFS for more info.
Did this doc help with your installation?
To find your integration data go to one.newrelic.com > All capabilities > Infrastructure > Third-party services and select the NFS integration link.
For more on how to find and use your data, see Understand and use integration data.
The NFS integration collects the following metrics:
These metrics are captured by default:
Total number of available bytes on disk.
Total number of bytes used.
Percentage of bytes used.
Total number of available bytes left on disk.
Percent of free space available on disk.
Total number of bytes read.
Total number of bytes written.
Number of bytes read per second.
Number of bytes written per second.
Number of read operations per second.
Number of write operations per second.
Total number of operations per second.
NFS version (will be either 3.0 or 4.0).
Mount point of NFS volume.
Additional metrics captured when
detailed_nfs is enabled (set to
true in the infrastructure configuration file):
Age in seconds of NFS client.
Number of times cached inode attributes are re-validated from the server.
Number of times cached dentry nodes are re-validated from the server.
Number of times an inode cache is cleared.
Number of times cached inode attributes are invalidated.
Number of times files or directories have been
Number of times a directory lookup has occurred.
Number of times permissions have been checked.
Number of updates (and potential writes) to pages.
Number of pages read directly via
Number of times a group of pages have been read.
Number of pages written directly via
Number of times a group of pages have been written.
Number of times directory entries have been read with
Number of times attributes have been set on inodes.
Number of pending writes that have been forcefully flushed to the server.
Number of times
Number of times locking has been attempted on a file.
Number of times files have been closed and released.
Number of times files have been truncated.
Number of times a file has been grown due to writes beyond its existing end.
Number of times a file was removed while still open by another process.
Number of times the NFS server gave less data than expected while reading.
Number of times the NFS server wrote less data than expected while writing.
Number of times the NFS server indicated
Number of NFS v4.1+ pNFS reads.
Number of NFS v4.1+ pNFS writes.
Number of times the client has had to establish a connection from scratch to the NFS server.
Number of times the client has made a TCP connection to the NFS server.
Duration (in jiffies, a kernel internal unit of time) the NFS mount has spent waiting for connections to the server to be established.
Duration since the NFS mount last saw any RPC traffic.
Number of RPC requests for this mount sent to the NFS server.
Number of RPC responses for this mount received from the NFS server.
Number of times the NFS server sent a response with a transaction ID unknown to this client.
A running er, incremented on each request as the current difference between sends and receives.
A running counter, incremented on each request by the current backlog queue size.
Maximum number of simultaneously active RPC requests ever used.
A running counter, incremented on each request as the current size of the sending queue.
A running counter, incremented on each request as the current size of the pending queue.
-1 in the infrastructure agent configuration file to avoid scraping NFS metrics.