Nagios

That helps me identify any failed package builds or packages I have built once, installed, and did not add to my package building system.

I can find that check in my Git repo of Nagios things.

Case in point," and there's a big glob of data there.

"I don't build my own FreeBSD base packages.

I do use that service sometimes for clients who want like a really quick and easy way to get some limited visibility into their systems.

But pretty famously, Alan and I both run Nagios.

We do our own monitoring system.

And when necessary, we even write our own plugins for it so that we monitor exactly what we want to monitor and do it exactly the way that we want to do it.

If you're going to try to load up more complex tasks on it, I would do all of the logic internally on that machine so that you're still limited to basically just an on-off sort of a reporting to healthchecks.io itself.

Keep in mind again that it's going to give you false positives every once in a while.

With Nagios, you have the concept of perf data.

So in addition to the exit code where you say, you know, this service is healthy or unknown or down or whatever, you get a little bit of extra data that you can send with it to kind of describe, you know, it's healthy and the ping is this much so that, you know, over time you can see how that's changing.