smokeping_probes_basevars(3) [debian man page]
Smokeping_probes_basevars(3) SmokePing Smokeping_probes_basevars(3) NAME
Smokeping::probes::basevars - Another Base Class for implementing SmokePing Probes OVERVIEW
Like Smokeping::probes::base, but supports host-specific variables for the probe. SYNOPSIS
*** Probes *** +basevars offset = 50% pings = 20 step = 300 # [...] *** Targets *** probe = basevars # if this should be the default probe # [...] + mytarget # probe = basevars # if the default probe is something else host = my.host DESCRIPTION
Provides the method `targets' that returns a list of hashes. The hashes contain the entries: addr The address of the target. vars A hash containing variables defined in the corresponding config section. tree The unique index that `probe::base' uses for targets. There's also the method 'vars' that returns the abovementioned hash corresponding to the 'tree' index parameter. VARIABLES
Supported probe-specific variables: 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 AUTHORS
Niko Tyni <ntyni@iki.fi> BUGS
Uses `Smokeping::probes::base' internals too much to be a derived class, but I didn't want to touch the base class directly. SEE ALSO
Smokeping::probes::base, Smokeping::probes::EchoPing 2.6.8 2013-03-17 Smokeping_probes_basevars(3)
Check Out this Related Man Page
Smokeping_probes_NFSping(3) SmokePing Smokeping_probes_NFSping(3) 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> 2.6.8 2013-03-17 Smokeping_probes_NFSping(3)