Uptime Kuma maybe
this post was submitted on 08 Dec 2023
44 points (100.0% liked)
Selfhosted
40152 readers
486 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Uptime Kuma can have a monitor that pings your gateway or google.com or something else on the Internet.
I'm not sure if it's simpler than smoke ping or not though, it's been too long since I used it
For me, it is easier than ~~smoking~~ smokeping. But smokeping offers more details by pinging the same host 20 times each run. This can help to discover packet loss.
Smoking is difficult
Smoking is easy. Stopping smoking is the hard one.
Statping-ng has had some updates beyond the base.
Snorkeling is probably your best choice as it did show latency overall and not just up/down.
Probably the only true way of knowing is by setting up an EXTERNAL host somewhere on a VPS or maybe a reputable VPS provider. Then, on that provider, set up Uptime Kuma, or if you don't want to go through that trouble and don't mind a potential 10 minute gap in knowing, https://uptimerobot.com/ which checks every 5 minutes and sends an alert.
Once you do this, unless you have a Static IP, you will want to register with a DDNS provider so you can then tell the uptime service to ping your DDNS host which should echo back . If your internet is down, it won't echo back and then it will trigger their alert. Of course, this won't work if your IP changes, so staying on top of that is key unless you use a router which auto updates it which a lot do now days.
Or, if you use Cloudflare Tunnels, it can be configured to alert you when the tunnel is down or unhealthy (A.K.A. No internet or the server is rebooted).
If you want it REALLY easy, you should be able to write a simple bash script that, when called, pings an arbitrary always online website like google, and if the ping returns an error, sends a telegram message to your phone. you could also store the current state in a separate file to allow for "is now down" and "is up again" differentiation, then use the telegram message timestamps to "track" (loosely used term) up- and downtime. To call the script, add it to your crontab and specify your test interval there.
Getting bash to send to telegram is ridiculously easy, as seen here: https://hackernoon.com/how-to-create-a-simple-bash-shell-script-to-send-messages-on-telegram-lcz31bx. This is EXTREMELY barebones, but it'll get the job done if you need zero bells and whistles.
Does telegram allow for local lan only messaging? If not, how does the bash script send the message to telegram?
I’ve landed on running uptime-kuma on my network, and when I get the “service restored” messages I know that I had an outage last night.
no, telegram is cloud based. you send the message via a CURL POST to the telegram API, which contains your bot token and message. details are in the linked guide.
Kuma obviously is more established and feature-proof, and will work great for most people who want notifications like this. I just wanted to take the prompt for a "simple alternative" overly serious 😎
But their internet is down, so it'll fail to send to telegram. Realistically it needs to be an external system that is tracking when it receives pings from the home network, so it can show periods where the bash script didn't ping for a while.
pfsense had tracking of the gateway built in, check your router to see if it already has something.
Since I already run netdata, I have set up a few ping checks. The results are graphed alongside other netdata charts.
Otherwise, the simplest method is going to be a custom shell script that feeds ping results to a plotting program like gnuplot.
What's the problem with smokeping though?
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HA | Home Assistant automation software |
| ~ | High Availability |
| IP | Internet Protocol |
| VPS | Virtual Private Server (opposed to shared hosting) |
3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #339 for this sub, first seen 8th Dec 2023, 22:15] [FAQ] [Full list] [Contact] [Source code]