smokeping_prober VS yet-another-cloudwatch-exporter

Check out the smokeping_prober. It generates high resolution histogram data that you can use to compare different paths.

I wrote this smokeping tool to monitor. I also use unpoller

I wrote this tool to monitor my ISP connectivity.

I am thinking this might be the exporter to use: https://github.com/SuperQ/smokeping_prober At the bottom of that page it says

I wrote a smokeping_prober for Prometheus.

For some stuff, I do end-to-end probin with a tool I wrote.

Smokeping Prober

I wrote a "better smokeping" tool that produces much more detailed data than IP SLA.

I wrote my own variation of smokeping. It currently only does ICMP and UDP probing, but I've thought about adding things like TCP, HTTP, DNS, etc.

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