net-test
yet-another-cloudwatch-exporter
Our great sponsors
| net-test | yet-another-cloudwatch-exporter | |
|---|---|---|
| 1 | 3 | |
| 41 | 862 | |
| - | 4.6% | |
| 0.0 | 9.3 | |
| almost 3 years ago | 8 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
net-test
-
Internet-monitoring – A Docker Stack which Monitors your home network
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.
yet-another-cloudwatch-exporter
-
Is it possible to have multiple 'label_values()' sources for a dashboard variable?
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.
-
Top 5 key metrics for monitoring AWS RDS
Monitoring AWS is pretty straightforward, using YACE to get data from AWS CloudWatch and store it in Prometheus.
-
Internet-monitoring – A Docker Stack which Monitors your home network
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
What are some alternatives?
Speedtest-Tracker - Continuously track your internet speed
node_exporter - Exporter for machine metrics
grafana-weathermap-panel - plugin weathermap for Grafana. This project is still in development.
joincap - Merge multiple pcap files together, gracefully.
smokeping_prober - Prometheus style smokeping
internet-monitoring - Monitor your network and internet speed with Docker & Prometheus
vaping - vaping is a healthy alternative to SmokePing!
Grafana-Mikrotik - 🔰 Grafana dashboard for Mikrotik/routerOS [Prometheus, SNMP]
speedtest-tracker - Speedtest Tracker is a self-hosted internet performance tracking application that runs speedtest checks against Ookla's Speedtest service.