Skip to content

RNET Status Monitor

I’ve launched using statping.

Statping sends ICMP, HTTP, and UDP messages to various services that operate on my servers as well as some 3rd party services. It’s pretty impressive, and was rather straight forward to install.

Now, I can foresee an issue with the method of installation I have taken. The correct way of setting something like this up would be on a platform external to the one that you are trying to monitor. Installing it on a VPS on some 3rd party provider would be ideal because if the monitored server goes down you need some way of at least being able to notify the admins that it’s down. That costs money, and isn’t quite a fun as running it yourself.

I’ve installed this on an LXC on my servers instead. With this method statping isn’t exactly sending queries over the net too. Albeit – it is pinging the WAN address, it’s not quite taking all the connection hops into account.

That being said, if either or is dead then that might be a good indicator that something is wrong.

Look, even though it’s not installed in an ideal environment it’s damn impressive. Installation took a solid 20 seconds as it fetched various scripts from GitHub using curl. It looks fantastic too, and supports for theme customisations. My only gripe is that it doesn’t support LDAP authentication, which I rely on heavily throughout various systems I operate.

I’m still using Grafana, and Prometheus node exporter on all my containers and VMs! Statping is just a pretty way of presenting statistics to external connections. For security purposes, Grafana can only be accessed from within the network.

Leave a Reply

Your email address will not be published. Required fields are marked *