If you need/want a dashboard it's kinda cool. There's a lot of other options that will do something similar, but not via SSH. Crontab can email you directly, no need for a service.
You could also just use systemd timers and do: systemctl --failed -t service
You are missing the biggest value offering here - service such as the one linked here (or healthchecks io that I personally use) will let you know that signal didn't arrive even when other things on your end failed (e.g. cron having a hard time sending failure email due to incorrect smtp credentials).
I use those kind of healthchecks literally for everything, especially for backups - they saved my ass many times over.
For things that actually matters to me, I use systemd timers, Prometheus and alert on failed services, but I do get that this might be a bit much for many setups.
You need some sort of external monitor for a missed pulse style alert. Personally I do something similar by collecting a "last success" metric with Prometheus and alerting on it with Grafana if the value is too far in the past. The local system cannot reliably alert if your job does not fail into the alert path or the system is just down.
I can see something like this being a great intermediate option to a full monitoring and alerting stack.
Because OP is trying to promote his project and get feedback, and you post about a competing product, to me the message is: don't look at the project OP wants you to check out, I've been using this instead and and it's amazing!
Who cares what you're using, I see show HN posts to be about OP's project, seems like a dick move to me to diverge attention to some other project. I just don't understand the motivation
The first thing I always want to know is, what does OP's project offer over pre-existing mature ones? Especially important when I'm seeing an increasing amount of projects that don't seem to even bother considering pre-existing projects.
I never read such comments in that way, the way I read them is actually like feedback to OP around benchmarking against competition.
Personally I love knowing about my competition, and it helps me with how I can differentiate and win over certain niches.
I don't know about OP, but I'm never offended by that, always grateful, helps me craft my message and delivery to the right audience and map out strategy.
I try not to over read into the open internet motivation behind end users, they may become customers, so I rather welcome them and seek to understand rather than judge.
Just goes against the spirit of people writing their own utils and sharing to me. Good on OP. They're not looking for money or fame here. If this util benefits one reader on HN it's worth it.
If it has context I appreciate them because it helps me make better informed decisions. Why not? HN isn't an editorials page exclusive for posters (except YC slop lol)
I've been toying with a similar idea for ~6 months: A lightweight job status dashboard.
I wanted something that required no setup, but could just push success/failure messages to as part of various cron jobs, windows tasks, and shell scripts we run throughout our organization.
The idea is kind of like "ntfy.sh", but for jobs status. You can send a "started" message at the beginning, update a "status" message periodically throughout the job, then send a "failed" message (optionally with logs) or a "success". Then a web dashboard gives you an overview with ability to drill down.
We use Icinga for monitoring and paging, but this just gives an overview for a quick look at things we don't want heavy duty monitoring on. Like my laptop backups, information about ansible runs across our fleet, etc.
You could just wrap cronic around the command and immediately receive the full output per mail when it fails. I don't see how a heartbeat alone without logs would help to identify temporary failures.
Your service could accomplish something similar if it had such a wrapper to report both success and failures with logs to a remote server. That would take away the need to run a local MTA, while also detecting with the heartbeat whether the job ran at all.
A temporary failure means that the job failed only once and then starts running again. If you want to investigate why it failed, you will need the output of that particular failed run.
There's currently no explicit "fail" ping, as that's not the main use case I care about. It's valid, though, and I've thought about adding it.
Being able to pipe logs to curl would also be useful. I'm concerned that people might accidentally send me private/sensitive data, but I'll consider it.
People seem to miss the point of the project. It’s not emailing you on failure. It’s emailing on missing reports of scheduled runs. If you rely on the job to report failure, the machine could go down. In that case you won’t get any email on the failed run.
Anyway, the TL;DR is: Create an endpoint, and if your script/cronjob fails to regularly ping it, you get notified (by email or ntfy). E.g.:
It also has an SSH TUI which is currently experimental and read-only, mostly because I'm not sure whether it is actually useful or just a gimmick :): To use it, simply add your SSH public key in your account settings.Yes, there are services like this already, and this is minimalistic by comparison. Feedback is welcome.
i have something similar at https://heartbeats.dorianmarie.com/
If you need/want a dashboard it's kinda cool. There's a lot of other options that will do something similar, but not via SSH. Crontab can email you directly, no need for a service.
You could also just use systemd timers and do: systemctl --failed -t service
You are missing the biggest value offering here - service such as the one linked here (or healthchecks io that I personally use) will let you know that signal didn't arrive even when other things on your end failed (e.g. cron having a hard time sending failure email due to incorrect smtp credentials). I use those kind of healthchecks literally for everything, especially for backups - they saved my ass many times over.
For things that actually matters to me, I use systemd timers, Prometheus and alert on failed services, but I do get that this might be a bit much for many setups.
You need some sort of external monitor for a missed pulse style alert. Personally I do something similar by collecting a "last success" metric with Prometheus and alerting on it with Grafana if the value is too far in the past. The local system cannot reliably alert if your job does not fail into the alert path or the system is just down.
I can see something like this being a great intermediate option to a full monitoring and alerting stack.
I'm myself very happy with https://healthchecks.io/ for this purpose.
I'll never understand commenting to show HNs with a link to competing products.
Why?
Because OP is trying to promote his project and get feedback, and you post about a competing product, to me the message is: don't look at the project OP wants you to check out, I've been using this instead and and it's amazing!
Who cares what you're using, I see show HN posts to be about OP's project, seems like a dick move to me to diverge attention to some other project. I just don't understand the motivation
It could help people. It's possible the sigabrt didn't even care to Google about Healthchecks.io before I decided to vibe code his own.
Also, what do you really think the odds are that sigabrt.dev will still exist in 2 years from now? Or 5?
The first thing I always want to know is, what does OP's project offer over pre-existing mature ones? Especially important when I'm seeing an increasing amount of projects that don't seem to even bother considering pre-existing projects.
I never read such comments in that way, the way I read them is actually like feedback to OP around benchmarking against competition.
Personally I love knowing about my competition, and it helps me with how I can differentiate and win over certain niches.
I don't know about OP, but I'm never offended by that, always grateful, helps me craft my message and delivery to the right audience and map out strategy.
I try not to over read into the open internet motivation behind end users, they may become customers, so I rather welcome them and seek to understand rather than judge.
Just goes against the spirit of people writing their own utils and sharing to me. Good on OP. They're not looking for money or fame here. If this util benefits one reader on HN it's worth it.
If it has context I appreciate them because it helps me make better informed decisions. Why not? HN isn't an editorials page exclusive for posters (except YC slop lol)
@altern8 you're dope for supporting folks putting themselves out there.
And it's open source!
And not blindly vibe coded.
I've been toying with a similar idea for ~6 months: A lightweight job status dashboard.
I wanted something that required no setup, but could just push success/failure messages to as part of various cron jobs, windows tasks, and shell scripts we run throughout our organization.
StatShed server: https://github.com/statshed/statshed-server StatShed go-cli: https://github.com/statshed/statshed-gocli
The idea is kind of like "ntfy.sh", but for jobs status. You can send a "started" message at the beginning, update a "status" message periodically throughout the job, then send a "failed" message (optionally with logs) or a "success". Then a web dashboard gives you an overview with ability to drill down.
We use Icinga for monitoring and paging, but this just gives an overview for a quick look at things we don't want heavy duty monitoring on. Like my laptop backups, information about ansible runs across our fleet, etc.
You could just wrap cronic around the command and immediately receive the full output per mail when it fails. I don't see how a heartbeat alone without logs would help to identify temporary failures.
https://habilis.net/cronic/
Your service could accomplish something similar if it had such a wrapper to report both success and failures with logs to a remote server. That would take away the need to run a local MTA, while also detecting with the heartbeat whether the job ran at all.
It does help. Sometimes jobs unexpectedly don't run at all.
A temporary failure means that the job failed only once and then starts running again. If you want to investigate why it failed, you will need the output of that particular failed run.
Thanks for the suggestion!
There's currently no explicit "fail" ping, as that's not the main use case I care about. It's valid, though, and I've thought about adding it.
Being able to pipe logs to curl would also be useful. I'm concerned that people might accidentally send me private/sensitive data, but I'll consider it.
People seem to miss the point of the project. It’s not emailing you on failure. It’s emailing on missing reports of scheduled runs. If you rely on the job to report failure, the machine could go down. In that case you won’t get any email on the failed run.
Context helps, shows intent, fosters discussion.
The pulse idea is neat. How do you handle jobs where the expected runtime is longer than the heartbeat interval?