net-test VS Speedtest-Tracker

Cool! It's so funny I just recently took an old bash script of mine which did something similar and have been upgrading it into a proper application which exports metrics to Prometheus and Grafana: https://github.com/Noah-Huppert/net-test

I saw a comment below where some was rolling their eyes that you "complicated" stuff with Prometheus, Grafana, and Docker and how you could just use Bash scripts and crons. As I just upgraded my codebase from this more bare metal approach to this "more complex setup" I'd like to mention: there's no way you could do time series statistical analysis easily with "just a cron job and a bash script". Prometheus and Grafana are for more than just buzz words. Prometheus offers an advanced time series database which allows you to, at minimum, do more robust analysis using data techniques like Histograms. As for Grafana, it makes exploring data dead easy. Providing users with a Docker Compose setup is also something I did with my tool and the benefits are huge. It lets me distribute a setup which relies on multiple moving parts working smoothly together. Sure I could write a whole wiki on how you should setup Prometheus Grafana and my tool, or I could distribute the setup with a configuration as code tool. Ensuring that even if someone doesn't want to use Docker Compose they can at least read my configuration as code and see exactly what I did to setup my tool.

here's the top two results if you search for "open speed test nginx reverse proxy": https://github.com/librespeed/speedtest/wiki/Reverse-proxy-with-Nginx https://github.com/henrywhitaker3/Speedtest-Tracker/issues/924

I have a WFH job but live in a rural area where the internet service is frequently unreliable. I'd like to monitor and log outage incidents (e.g. time of incident, duration) so that I can provide that data to my local service provider and get some real assistance in solving the problem. I have been using a small container app called SpeedTest Tracker which helps, but it's fairly heavyweight for what I want to accomplish. I'd like to (1) get longer historical data (e.g. ~90 days reporting), (2) get more granular reporting intervals (e.g. every 5-15min), and (3) more lightweight in the test payload (e.g. simple ping as opposed to large data transfer).

https://github.com/henrywhitaker3/Speedtest-Tracker this is what I use to track my internets up and down speeds.

oh if it's the actual speed you're interested in... see on my dashboard there are two speedtest panels in the 'monitoring' section? those are two instances of this - https://github.com/henrywhitaker3/Speedtest-Tracker - one running on each machine and they test the speed at regular intervals and keep a log.

Never mind -- Found it, https://github.com/henrywhitaker3/Speedtest-Tracker for anyone interested.

Not sure if this is what he's using but I use https://github.com/henrywhitaker3/Speedtest-Tracker

I would also add Speedtest-Tracker so you can make sure your getting speeds for which you pay for, It keeps historical data so you can go back a bit, I have my testing every 30 minutes. The default is once an hour.

Essentially I'm looking for something similar to this Speedtest Tracker, but where I can specify the iperf3 server(s) to test against.