this post was submitted on 04 Jul 2026
24 points (100.0% liked)

Programming

27631 readers
211 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
 

I run a few side projects and I've gone through different stages of monitoring them. First it was just checking manually if the site loads. Then I added a simple curl ping in cron. Then I started tracking response times, certificate expiry, even visual changes on pages.

At some point I realized I was spending more time building monitoring than the actual product. Classic trap.

Curious what other devs use for keeping an eye on their stuff. Do you go with a hosted service, self-host something like Uptime Kuma, or just wing it with scripts?

you are viewing a single comment's thread
view the rest of the comments
[–] hendrik@palaver.p3x.de 4 points 5 days ago* (last edited 5 days ago)

Isn't there a bunch of good monitoring solutions and all you need to configure is, X should be reachable, or it should answer with a HTTP status code 200. And that's the needed effort per service?

Idk which monitoring software is best of as today, here's a list: https://github.com/awesome-foss/awesome-sysadmin#monitoring--status-pages

I guess there's lots of edge cases, though. Testing whether some web form still triggers an email in your inbox is probably something that requires custom logic.