NAME

       Smokeping::probes::NFSping - NFSping Probe for SmokePing

SYNOPSIS

        *** Probes ***

        +NFSping

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

        # [...]

        *** Targets ***

        probe = NFSping # if this should be the default probe

        # [...]

        + mytarget
        # probe = NFSping # if the default probe is something else
        host = my.host

DESCRIPTION

       Integrates NFSping as a probe into smokeping. The variable binary must point to your copy
       of the NFSping program.

       NFSping can be downloaded from:

       <https://github.com/mprovost/NFSping>

       In blazemode, NFSping sends one more ping than requested, and discards the first RTT value
       returned as it's likely to be an outlier.

VARIABLES

       Supported probe-specific variables:

       binary
           The location of your nfsping binary.

           Example value: /usr/local/bin/nfsping

           This setting is mandatory.

       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 acqusition 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. Note that 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.

           Example value: 20

       step
           Duration of the base interval that this probe should use, if different from the one
           specified in the 'Database' section. Note that 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

       timeout
           The nfsping "-t" parameter, but in (possibly fractional) seconds rather than
           milliseconds, for consistency with other Smokeping probes.

           Example value: 1.5

AUTHORS

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