23
What's your approach to monitoring side projects without overengineering it? (lemmy.world)
submitted 4 months ago by to c/programming@programming.dev
7 comments fedilink hide all child comments
 

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
[–] 5 points 4 months ago* (last edited 4 months 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 for example whether some web form still triggers an email in your inbox is probably something that requires custom logic.

  • permalink
  • fedilink
  • source
    •