Speedtest-Tracker VS yet-another-cloudwatch-exporter

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.

OK, I found this yace issue https://github.com/nerdswords/yet-another-cloudwatch-exporter/issues/34 which pointed me to prometheus re-labeling: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config. I suspect this will resolve my need.

Monitoring AWS is pretty straightforward, using YACE to get data from AWS CloudWatch and store it in Prometheus.

There's also script exporters (a few implementations) for simpler Nagios style checks and more specialised ones for getting things like Cloudwatch data (shout out to YACE[1] - with dashboards from promcat). It's really quite vibrant the ecosystem.

[1] https://github.com/ivx/yet-another-cloudwatch-exporter