NFS
Bleemeo monitors NFS through automatic service detection and built-in metrics gathered from /proc/self/mountstats.
Auto-Detection
Section titled “Auto-Detection”Glouton automatically detects NFS mounts on your server. If NFS is not detected automatically, you can enable it manually.
sudo tee /etc/glouton/conf.d/99-nfs.conf > /dev/null << 'EOF'service: - type: "nfs"EOFCreate or edit C:\ProgramData\glouton\conf.d\99-nfs.conf:
service: - type: "nfs"Built-in Metrics
Section titled “Built-in Metrics”| Metric | Description |
|---|---|
nfs_ops | Number of operations executed per second |
nfs_transmitted_bits | Data exchanged in bits per second |
nfs_rtt_per_op_seconds | Average round-trip time per operation in seconds |
nfs_retrans | Number of times an operation had to be retried per second |
Monitoring Troubleshooting
Section titled “Monitoring Troubleshooting”See Troubleshoot a Service Check or Missing Metrics for what applies to every service: finding the address and port Glouton really uses, what each check message means, and how to read the collection error — which does not appear in the agent logs at the default level.
The Service Check is not OK
Section titled “The Service Check is not OK”NFS is the one detected service for which Glouton creates no service check:
a running client process says nothing useful about whether the shares are
actually usable, so no service_status is reported. A hung or stale mount will
not turn anything critical here — alert on the metrics listed above, or on a
custom check of your own.
Metrics are Missing
Section titled “Metrics are Missing”The metrics are read from /proc/self/mountstats, filtered to the READ and
WRITE operations.
Reproduce what Glouton does, from the machine where the agent runs:
grep -A 5 "nfs" /proc/self/mountstats | head -20| What you see | Cause | Fix |
|---|---|---|
grep nfs /proc/self/mountstats returns nothing |
No NFS share is mounted | The metrics only exist for mounted shares; mount one |
mountstats inside the container does not list the shares |
The agent runs in a container without the host mounts | Give the agent container the host mount namespace, or install the agent on the host |
| the counters exist and stay flat | The share is mounted but idle | Nothing to fix: rates are zero when no read or write happens |
| other NFS operations are absent by design | Only READ and WRITE show up |
Glouton deliberately limits collection to those two operations |