Smokeping_probes_DNS(3)
π NAME π
Smokeping::probes::DNS β Name Service Probe for SmokePing. That's the whole title, bestie, and yes we're about to make DNS probing make sense. β¨
π¦ SYNOPSIS π¦
Okay so here's the config vibe, exactly as it shows up:
*** Probes ***
+DNS
binary = /usr/bin/dig # mandatory
forks = 5
offset = 50%
step = 300
timeout = 15
# The following variables can be overridden in each target section
/^influx_.+/ = influx_location = In the basement
lookup = www.example.org
pings = 5
server = ns1.someisp.net
# [...]
*** Targets ***
probe = DNS # if this should be the default probe
# [...]
+ mytarget
# probe = DNS # if the default probe is something else
host = my.host
/^influx_.+/ = influx_location = In the basement
lookup = www.example.org
pings = 5
server = ns1.someisp.net
πΈ DESCRIPTION πΈ
This probe integrates dig as a probe into SmokePing. The variable binary must point to your copy of the dig program. If it is not installed on your system yet, you should install bind-utils >= 9.0.0. π«Ά
The probe asks the given host for its name n times, where n is the amount specified in the config file. Literally that simple, and it's giving useful. π
β¨ VARIABLES β¨
Two flavors here: probe-specific and target-specific. Don't skip, bestie, because defaults and mandatory settings live in here. π
π Supported probe-specific variables
binaryβ The location of yourdigbinary. Example value:/usr/bin/dig. This setting is mandatory. π¨forksβ Run this many concurrent processes at maximum. Example value:5. Default value:5. π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-specificoffsetparameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively asrandom, and the offset from theGeneralsection 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 variableconcurrentprobesis set in theGeneralsection.) Example value:50%. π°οΈstepβ Duration of the base interval that this probe should use, if different from the one specified in theDatabasesection. Note that the step in the RRD files is fixed when they are originally generated, and if you change thestepparameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variableconcurrentprobesis set in theGeneralsection.) Example value:300. πtimeoutβ How long a singlepingtakes at maximum. Example value:15. Default value:5. β³
π Supported target-specific variables
/^influx_.+/β This is a tag that will be sent to influxdb and has no impact on the probe measurement. The tag name will be sent without the"influx_"prefix, which will be replaced with"tag_"instead. Tags can be used for filtering. Example value:influx_location = In the basement. π·οΈlookupβ Name of the host to look up in the dns. Example value:www.example.org. π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:5. π―serverβ Name of the dns server to use. Example value:ns1.someisp.net. π
π AUTHORS π
Igor Petrovski <pigor@myrealbox.com>,Carl Elkins <carl@celkins.org.uk>,Andre Stolze <stolze@uni-muenster.de>,Niko Tyni <ntyni@iki.fi>,Chris Poetzel<cpoetzel@anl.gov>
And that's the page, bestie! π This is from SmokePing version 2.9.0, dated 2025-06-30, and it's the Smokeping_probes_DNS(3) manual. Bye, love you, go probe responsibly π«Άβ¨
π¦ where this page comes from
- alpine 3.23: smokeping-doc 2.9.0-r1 Β· GPL-2.0-or-later
- alpine 3.24: smokeping-doc 2.9.0-r1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms