This repository provides two speedtest probes for Smokeping. speedtest.pm uses speedtest-cli by @sivel (https://github.com/sivel/speedtest-cli), while speedtestcli.pm uses the official Ookla Speedtest CLI program (https://www.speedtest.net/apps/cli). Details about both below:
Integrates speedtest-cli (https://github.com/sivel/speedtest-cli) as a probe into smokeping. The variable binary must
point to your copy of the speedtest-cli program. If it is not installed on
your system yet, you should install the latest version from https://github.com/sivel/speedtest-cli. Note that you need at least version >=2.0.2 for speedtest-cli.
The Probe asks for the given resource one time, ignoring the pings config variable (because pings can't be lower than 3).
You can ask for a specific server (via the server parameter) and record a specific output (via the measurement parameter).
Note that you may want to change speedtest's forks parameter because basically: by default smokeping runs up to 5 speedtest probes at once, skewing overall results and possibly running into resource trouble on low spec devices. Setting forks = 1 will alleviate these issues.
Parameters:
binary=> The location of your speedtest-cli binary.server=> The server id you want to test against (optional). If unspecified, speedtest.net will select the closest server to you. The value has to be an id reported by the command speedtest-cli --listmeasurement=> What output do you want graphed? Supported values are: ping, download, uploadextraargs=> Extra arguments to send to speedtest-cli
You can use extraargs with --no-download or --no-upload if you want to skip some test direction (https://github.com/sivel/speedtest-cli/commit/3feb38d9d47d41e6b0679e3722dedb4511c437f6).
Integrates Ookla speedtest CLI (https://www.speedtest.net/apps/cli) as a probe into smokeping. The variable binary must
point to your copy of the speedtest program. If it is not installed on
your system yet, you should install the latest version from https://www.speedtest.net/apps/cli.
The Probe asks for the given resource one time, ignoring the pings config variable (because pings can't be lower than 3).
You can ask for a specific server (via the server parameter).
Note that you may want to change speedtest's forks parameter because basically: by default smokeping runs up to 5 speedtest probes at once, skewing overall results and possibly running into resource trouble on low spec devices. Setting forks = 1 will alleviate these issues.
Parameters:
binary=> The location of your speedtest binary.server=> The server id you want to test against (optional). If unspecified, speedtest.net will select the closest server to you. The value has to be an id reported by the command speedtest-cli --list or speedtest -Lmeasurement=> What output do you want graphed? Supported values are: download, upload, pingextraargs=> Extra arguments to send to speedtest
The speedtest.pm and speedtestcli.pm should be copied into your smokeping installation directory - for instance here: /opt/smokeping/lib/Smokeping/probes/
You can get logs of what goes on inside the plugin either by running smokeping with --debug, or by changing this line:
#set to LOG_ERR to disable debugging, LOG_DEBUG to enable it
setlogmask(LOG_MASK(LOG_ERR));
to
#set to LOG_ERR to disable debugging, LOG_DEBUG to enable it
setlogmask(LOG_MASK(LOG_DEBUG));
After doing this (and restarting smokeping), the plugin's logs will go to syslog, local0.debug. You will need something like
local0.* /var/log/local.log
in your syslog configuration.
### Add this to your Probes file in conf.d folder
+ speedtest
binary = /usr/local/bin/speedtest-cli
timeout = 300
forks = 1
step = 3600
offset = random
pings = 3
++ speedtest-download
measurement = download
++ speedtest-upload
measurement = upload
++ speedtest-upload
measurement = ping
+ speedtestcli
binary = /usr/bin/speedtest
timeout = 300
forks = 1
step = 3600
offset = random
pings = 3
++ speedtestcli-download
measurement = download
++ speedtestcli-upload
measurement = upload
++ speedtestcli-upload
measurement = ping
### Add these to your Targets file.
++++ download_from_NextGen_Communications_via_speedtest_cli
menu = download_from_NextGen_Communications_via_speedtest_cli
title = download_from_NextGen_Communications_via_speedtest_cli
probe = speedtest-download
server = 1737
measurement = download
host = dummy.com
++++ upload_to_NextGen_Communications_via_speedtest_cli
menu = upload_to_NextGen_Communications_via_speedtest_cli
title = upload_to_NextGen_Communications_via_speedtest_cli
probe = speedtest-upload
server = 1737
measurement = upload
host = dummy.com
++++ download_from_NextGen_Communications_via_speedtest_ookla
menu = download_from_NextGen_Communications_via_speedtest_ookla
title = download_from_NextGen_Communications_via_speedtest_ookla
probe = speedtestcli-download
server = 1737
measurement = download
host = dummy.com
++++ upload_to_NextGen_Communications_via_speedtest_ookla
menu = upload_to_NextGen_Communications_via_speedtest_ookla
title = upload_to_NextGen_Communications_via_speedtest_ookla
probe = speedtestcli-upload
server = 1737
measurement = upload
host = dummy.com
- Currently the probe's unit of measurement is hardcoded to "bps". This will be a problem if you want to measure "ping", which is reported in seconds.
- For large values the overview graphs will have wrong data. You need to add something like this to your overview section of your Smokeping config:
+overview
max_rtt = 1000000000
- In order for the RRD to actually store data larger than 180, you also need to apply this patch (or to use the most recent version of smokeping): https://github.com/oetiker/SmokePing/commit/60419834f224a0735094fd4ad0aac8eac3b15289
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent
