Speedtestplusplus

A easy to setup speedtest worker for speedtest.net based on speedtestplusplus (https://github.com/taganaka/SpeedTest).

As this supports raw tcp and aggressive multithreading it can act as a more precise replacement for the "standard" speedtest.net collector https://hub.docker.com/r/atribe/speedtest-for-influxdb-and-grafana/ which are all based on the speedtest-cli by swivel.

Be nice, this is my first repo.

Blog: https://www.valki.com/dockerized-speedtest/

Dockerimage @ Dockerhub: https://hub.docker.com/repository/docker/valki/speedtestplusplus

Github Sources: https://github.com/valki2/Speedtestplusplus

Installation instructions

Optional: Build the image (as you may pull this image from dockerhub too)

git clone https://github.com/valki2/Speedtestplusplus

then enter the created repo and build your image

cd Speedtestplusplus

docker build --tag="valki/speedtestplusplus" .

Set up your docker network

To tangle everything together please create a network for your containers called speedtestnet. You can click through a tool like portainer or just use the docker command somehow like this:

docker network create speedtestnet --driver=bridge --subnet=172.29.99.0/22 --ip-range=172.29.99.0/25 --gateway=172.29.99.1 

Fire up the docker containers

In order to store the collected data we need an influxdb container... or feel free to use your existing instead!

docker run --name influxdb --hostname influxdb --net speedtestnet -d --restart always -e INFLUXDB_ADMIN_USER=admin -e INFLUXDB_ADMIN_PASSWORD=password -e INFLUXDB_DB=speedtest -v speedtest_influxdb:/var/lib/influxdb influxdb:1.5

Finally fire up your speedtestplusplus worker container

docker run -d --name=speedtest --net speedtestnet -d --restart always -e SPEEDTEST_INTERVAL=600 -e SPEEDTEST_HOST=local valki/speedtestplusplus

SPEEDTEST_HOST is to distinct multiple instances in one database

SPEEDTEST_INTERVALL is the time in seconds between the tests

TESTSERVER is use a specific testserver (https://telcodb.net/explore/speedtest-servers/) instead of letting the tool find the best one. Example: -e TESTSERVER=speedtest.telfs.com:8080

Optional - Grafana

You may want a grafana instance for your funny little trees eeeh dashboard...

docker run --name grafana --hostname grafana --net speedtestnet -d --restart always -p 3000:3000 -v speedtest_grafana:/etc/grafana/provisioning -v grafana-storage:/var/lib/grafana -e GF_SERVER_ROOT_URL=http://localhost -e GF_SECURITY_ADMIN_PASSWORD=admin -e GF_AUTH_ANONYMOUS_ENABLED=true grafana/grafana:latest

Configure Grafana Dashboard

1. Login with admin:admin and set a new password!
2. Create a new dashboard with the attached json code

OPTIONAL: external cronjob

In case your connection is very unstable, it is possible that the container just hangs there and no test can finish. For that reason i created another tag "_once" - instead of using the cron inside of the container, this flavour uses your hosts cronjob to call a shellscript which launches the speedtest container. After each run, the container is exited and removed before the next launch.

Just use the "_once" docker-compose file and rename it, then fire up with docker compose as usual.

Exemplary cronjob on your host: */10 * * * * /share/Backup/docker/speedtest/exec_speedtest.sh >/dev/null 2>&1