Programming

I guess I don't have many hosted side projects. Those I do, I don't put them on separate domains. I doubt people use or care, so I haven't added monitoring for individual projects specifically. I guess I could and should do that now that I established my own online monitoring without third-party free tier limitations.

I use Red Sift (free) for certificate monitoring, since Let's Encrypt dropped expiry warning notifications. Given it's automated, it's never been an issue for my self-managed projects, though.

For is-online/is-reachable monitoring, after free services I used became more restricted, and none matched my simple needs, I created Meercat Monitor, which runs on my server and checks some of my and work related projects/services. Simple checks scheduled checks, email notification, and a simple history and status view. Something simple enough and open source so I can audit and manage sources.

If it's a side project, then by definition I'm doing it for fun or to build certain skills, not as some sort of "product". Personally, I don't do "professional" work outside of my job.

But yeah, getting sidetracked is absolutely a classic trap.

At risk of sidetracking more, could you turn the monitoring you're doing into its own project or something at least re-usable?

If not, I'd either self-host something or just continue using what you've made as-is.

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.

So, first, it's important to know that monitoring is not the same thing as measuring service levels to adhere to some SLA (service-level agreement, a promise to some customer). We have jargon for the latter; we say that we are measuring SLIs (service-level indicators) and checking them against SLOs (service-level objectives). An SLA is kind of like a set of SLOs.

For monitoring, in general, I recommend Prometheus-style metrics. I do not recommend OpenTelemetry in any encoding; it is far too complex compared to one metric per line of plain text. To keep metrics private, you can either scrape over SSH, scrape over an admin interface, scrape over LAN, or scrape over localhost-only listeners; read the documentation for your service's metrics-exporting tool. AlertManager, from the reference Prometheus suite, is a great way to get pinged on SMS/Pushover/Signal/etc. when something is down or broken.

For SLAs, I just set up an Uptime Kuma for a small business. It's a pretty good tool for SLAs and basic notifications in Slack/Mattermost/IRC/etc. but not capable of doing much more than uptime/ping checks.

I can't recommend any hosted service in good faith. You're not going to ever be able to price-justify it; self-hosting will always be more cost-effective. And since the hosted service isn't going to have your runbook or credentials or experience, what can they really do besides ping you? Pay $5/mo to your cloud provider instead of over $20/mo to a hosted metrics scraper or dashboard host.

I have my (1) project as homepage, if it doesn't load on browser startup then I have ze problem. (I am a monster with disabled tab restoring.)

IDK what I will do if I will have more than one, but that's future me problem.

If i cant do it in a weekend i usually hire someone.

...unless it brings me joy. Then its fun like setting up my miyoo mini plus with a cystom pokrmon theme.

Currently using UptimeRobot, but have used a few different products over the years.