Oxidized VS uptime-kuma

after using expect and TCL heavily for years, I can firmly say they suck at scale.

Ruby https://github.com/ytti/oxidized/blob/master/lib/oxidized/mo...

Oxidized supports PFSense natively - https://github.com/ytti/oxidized/blob/master/lib/oxidized/model/pfsense.rb

Oxidized? https://github.com/ytti/oxidized

Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized

Check out Oxidized

You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email.

Uptime Kuma can also monitor certificate expiration; you can also enable it to show you how many days are left until it expires.

https://github.com/louislam/uptime-kuma

2. Uptime Kuma

- Web terminal & live logs

I'm trying it as an alternative to Portainer and I'm loving it. It seems to fit perfectly in my flow.

Code and more info: https://github.com/louislam/uptime-kuma

(Not affiliated, just a happy user)

FYI - Uptime Kuma supports push-based monitoring as well.

Uptime-Kuma for Watching Services

I have tunnel up and running as described on this page: https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy-with-Cloudflare-Tunnel

⭐ Uptime-kuma on GitHub

Uptime Kuma is a self-hosted monitoring service that you can use to keep track of the heath of your applications, websites, and APIs. You can configure it to watch services with different types of health checks and set up email notifications for when there are problems. Uptime Kuma also lets you design custom status pages that you can use to share public information about your service health statuses and to manage incidents.