Smokeping_probes_EchoPingSmtp(3)
π NAME π
Smokeping_probes_EchoPingSmtp(3) β welcome to the SmokePing probe page for Smokeping::probes::EchoPingSmtp, an echoping(1) probe for SmokePing. Yes bestie, it's giving mail-server latency realness.
π¦ OVERVIEW π¦
Measures SMTP roundtrip times (mail servers) for SmokePing. Literally that's the whole vibe.
β¨ SYNOPSIS β¨
*** Probes ***
+EchoPingSmtp
binary = /usr/bin/echoping
forks = 5
offset = 50%
step = 300
# The following variables can be overridden in each target section
/^influx_.+/ = influx_location = In the basement
extraopts = -some-letter-the-author-did-not-think-of
ipversion = 4
pings = 5
priority = 6
timeout = 1
tos = 0xa0
waittime = 1
# [...]
*** Targets ***
probe = EchoPingSmtp # if this should be the default probe
# [...]
+ mytarget
# probe = EchoPingSmtp # if the default probe is something else
host = my.host
/^influx_.+/ = influx_location = In the basement
extraopts = -some-letter-the-author-did-not-think-of
ipversion = 4
pings = 5
priority = 6
timeout = 1
tos = 0xa0
waittime = 1
π VARIABLES π
π Supported probe-specific variables π
binaryβ The location of your echoping binary. Default value:/usr/bin/echopingforksβ Run this many concurrent processes at maximum. Example value:5. Default value:5offsetβ 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%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
π¦ 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 basementextraoptsβ Any extra options specified here will be passed unmodified toechoping(1). Example value:-some-letter-the-author-did-not-think-ofipversionβ The IP protocol used. Possible values are"4"and"6". Passed toechoping(1)as the"-4"or"-6"options. Example value:4pingsβ 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:5priorityβ The"-p"echoping(1)option. Example value:6timeoutβ The"-t"echoping(1)option. Example value:1. Default value:5tosβ The"-P"echoping(1)option. Example value:0xa0waittimeβ The"-w"echoping(1)option. Example value:1
π AUTHORS π
Niko Tyni <ntyni@iki.fi>
π§ NOTES π§
Heads up bestie: thefill,sizeandudpEchoPing variables are not valid. No cap, those ones are a no-go.
π SEE ALSO π
Smokeping::probes::EchoPing
This page is from SmokePing version 2.9.0, dated 2025-06-30 β bye bestie, go measure those SMTP roundtrips and slay π«Ά
π¦ 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