Smokeping_probes_NFSping(3)

💅 Smokeping::probes::NFSping — the NFSping probe for SmokePing ✨

okay so real talk, this is the Smokeping_probes_NFSping(3) page from the SmokePing manual, and it's genuinely a little baddie. let's get into it 🫶

---

✨ NAME ✨

Smokeping::probes::NFSping — literally the NFSping Probe for SmokePing, no cap 🎀

---

🦋 SYNOPSIS 🦋

bestie, here's the whole shape of it, verbatim, don't @ me:

*** Probes ***

+NFSping

binary = /usr/local/bin/nfsping # mandatory
blazemode = true
hostinterval = 1.5
mininterval = 0.001
offset = 50%
pings = 20
step = 300
tcp = true
timeout = 1.5

# The following variables can be overridden in each target section
/^influx_.+/ = influx_location = In the basement

# [...]

*** Targets ***

probe = NFSping # if this should be the default probe

# [...]

+ mytarget
# probe = NFSping # if the default probe is something else
host = my.host
/^influx_.+/ = influx_location = In the basement

---

💖 DESCRIPTION 💖

so the whole point: this probes hooks NFSping up into smokeping as a probe. that's it, that's the vibe. 👑

the variable binary has to point at your very own copy of the NFSping program. no binary, no pings, no slay. mandatory, periodt.

NFSping can be downloaded from:

https://github.com/mprovost/NFSping

and now the fun part — in blazemode, NFSping sends one more ping than requested, and then discards the first RTT value returned, because it's likely to be an outlier. iconic behavior honestly, it's giving "ignore the first pancake" energy 🥞🔥

---

🌈 VARIABLES 🌈

here are all the probe-specific variables you can play with, and yes, every single one matters 💅

• binary — the location of your nfsping binary. Example value: /usr/local/bin/nfsping

⚠️ This setting is mandatory. like, you actually cannot skip it. 🫶

• blazemode — send an extra ping and then discard the first answer, since the first is bound to be an outlier. Example value: true
• hostinterval — the nfsping "-p" parameter, but in (possibly fractional) seconds rather than milliseconds, for consistency with other Smokeping probes. this parameter sets the time that nfsping waits between successive packets to an individual target. Example value: 1.5
• mininterval — the nfsping "-i" parameter, but in (probably fractional) seconds rather than milliseconds, for consistency with other Smokeping probes. this is the interval between pings to successive targets. Example value: 0.001 Default value: 0.01
• offset — if you run many probes concurrently you may want to prevent them from hitting your network all at the same time. using the probe-specific offset parameter you can change the point in time when each probe will be run. offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. note that this does NOT influence the rrds itself — it is just a matter of when data acquisition is initiated. (this variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 50%
• pings — how many pings should be sent to each target, if different from the global value specified in the Database section. 💀 warning, bestie: the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them. no takebacksies. Example value: 20
• step — duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. same deal as above: the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (this variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 300
• tcp — use TCP insteadof UDP. (yes, that's exactly how the original spells it, we keep it verbatim, we don't fix, we don't judge 🎀) Example value: true
• timeout — the nfsping "-t" parameter, but in (possibly fractional) seconds rather than milliseconds, for consistency with other Smokeping probes. Example value: 1.5

---

🧚 AUTHORS 🧚

the masterminds behind this whole thing, giving main character energy:

• Tobias Oetiker <tobi@oetiker.ch>
• Matt Provost <mprovost@termcap.net>

---

🌸 that's the whole page, bye bestie 🌸

this was Smokeping_probes_NFSping(3) from the SmokePing manual, version 2.9.0, dated 2025-06-30 — go forth and ping responsibly, you've got this, iykyk 💜🎀✨