u/RayZen23

How it works:

-Append && curl -fsS https://ping-url to a cron job. If the ping doesn't arrive within the expected interval + grace, the monitor flips to down.

-Also does HTTP uptime checks (interval, expected status range, keyword match, SSL expiry).

The part i actually care about: pings can carry metrics as query params (?rows=1400), and you set rules on them; floor, ceiling, or deviation from the recent median.

So ?rows=0 fails against a floor even though the job "succeeded." Lets you treat "ran but processed nothing" as a down state.

Alerts go to email/Telegram/Slack/Discord/webhook; webhook payloads are HMAC-signed so you can automate a response.

Currently working on incorporating auto analyzing stack traces in stderr payloads.

Looking for feedback, would you find this useful ?

Link : https://pulsewatcher.vercel.app/

How it works:

-Append && curl -fsS https://ping-url to a cron job. If the ping doesn't arrive within the expected interval + grace, the monitor flips to down.

-Also does HTTP uptime checks (interval, expected status range, keyword match, SSL expiry).

The part i actually care about: pings can carry metrics as query params (?rows=1400), and you set rules on them; floor, ceiling, or deviation from the recent median.

So ?rows=0 fails against a floor even though the job "succeeded." Lets you treat "ran but processed nothing" as a down state.

Alerts go to email/Telegram/Slack/Discord/webhook; webhook payloads are HMAC-signed so you can automate a response.

Currently working on incorporating auto analyzing stack traces in stderr payloads.

Looking for feedback, would you find this useful ?

Link : https://pulsewatcher.vercel.app/

How it works:

-Append && curl -fsS https://ping-url to a cron job. If the ping doesn't arrive within the expected interval + grace, the monitor flips to down.

-Also does HTTP uptime checks (interval, expected status range, keyword match, SSL expiry).

The part i actually care about: pings can carry metrics as query params (?rows=1400), and you set rules on them; floor, ceiling, or deviation from the recent median.

So ?rows=0 fails against a floor even though the job "succeeded." Lets you treat "ran but processed nothing" as a down state.

Alerts go to email/Telegram/Slack/Discord/webhook; webhook payloads are HMAC-signed so you can automate a response.

Currently working on incorporating auto analyzing stack traces in stderr payloads.

Looking for feedback, would you find this useful ?

Link : https://pulsewatcher.vercel.app/

The idea is stupidly simple: you add one line to the end of your cron job :

>!0 3 * * * ./backup.sh && curl -fsS https://your-ping-url > /dev/null!<

Link: [Pulsewatch](https://pulsewatcher.vercel.app)

A tool that tells you when your cron jobs silently stop running.

You get an alert (email, Telegram, or webhook, works with Slack/Discord). It also does uptime monitoring: it checks your site every few minutes and pings you when it's down, with public status pages included.

I'm a solo dev and this is freshly launched, so I'd genuinely love feedback.

(dm me for 100% promo code, i'd love some serious feedback)

If the ping doesn't arrive on schedule, you get an alert (email, Telegram, or webhook, works with Slack/Discord).

It also does uptime monitoring: it checks your site every few minutes and pings you when it's down, with public status pages included.

I'm a solo dev and this is freshly launched, so i'd genuinely love feedback.

The idea is stupidly simple: you add one line to the end of your cron job.

>!0 3 * * * ./backup.sh && curl -fsS https://your-ping-url > /dev/null!<

If the ping doesn't arrive on schedule, you get an alert (email, Telegram, or webhook, works with Slack/Discord).

It also does uptime monitoring: checks your site every few minutes and pings you when it's down, with public status pages included.

I'm a solo dev and this is freshly launched, so i'd genuinely love feedback.