GitHub - oetiker/SmokePing: The Active Monitoring System
github.com
external-link
The Active Monitoring System. Contribute to oetiker/SmokePing development by creating an account on GitHub.

My Internet goes down fairly often so I want to start keeping track of it.

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.

Romanmir
link
fedilink
English
21Y

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 😎

Geronimo Wenja
link
fedilink
English
71Y

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.

Create a post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 157 users / day
  • 444 users / week
  • 1.17K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.69K Posts
  • 74.2K Comments
  • Modlog