SmokePing (FastCGI) + Caddy 的設定
Cloudflare oopsie just now
@dillo I got it running here now: https://smokeping.melroy.org/
I just setup it up. Although I'm also running Grafana (Like: https://stats.melroy.org/public-dashboards/f628b3a1abe5417fa9549c0a210c953d?orgId=1&refresh=5m)
Smokeping has its own web interface. It should be feasible to create fping with influxdb/Prometheus and create graphs in Grafana as well. But for now I just setuped https://smokeping.melroy.org/
@dillo I there. There is another tool, which I like even more. It's called #fping and #smokeping https://github.com/oetiker/SmokePing. And they just released a new version v2.9.0: https://oss.oetiker.ch/smokeping/pub/smokeping-2.9.0.tar.gz. Smokeping is using fping under the hood. You can also run fping solo.
Anyhow, here are my results of just the ping command:
--- google.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 20287ms
rtt min/avg/max/mdev = 6.139/7.144/8.523/0.586 ms
More progress on the #homelab renovation.. mostly software-related at the moment though. Managed to get #nomad to correctly mount the NFS volumes I needed for #smokeping and #mariadb, and figured out how template files work for simple config files being passed in to containers.
I'm currently using my old #unraid server as the storage backend.. but I'll most likely still be upgrading to a new unraid server soon so what I setup now can easily be translated to the next server. Once I have everything transferred I'll setup a backup task across the storage on unraid so that I have all application states protected.
Last thing to figure out is the load balancing for my services. I want them all accessible via IP/port on my LAN and by service under #tailscale. Not sure how this will all fit together - I probably need a dedicated box for the LB.. maybe just a simple #nginx proxy with #consul configuration so that it's somewhat dynamic. Would love to get feedback on this, and if you know of a simpler/better way!
You can now find some #smokeping graph on #BoxyBSD's status page: https://boxybsd.com/status/
Do you miss any destination? Let us know!