返回资讯中心
外部精选
软件工程
#开发者实时流

Cronomonitor.com Is Now Live

Paste your crontab and know the moment any job doesn't run, fails or slows down, with its output to hand. Plus a status page for every project, from £9/month with unlimited checks.

Hacker News 最新iambenc2026/10/19 · 27 天前11 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Paste your crontab and know the moment any job doesn't run, fails or slows down, with its output to hand. Plus a status page for every project, from £9/month with unlimited checks.

One line of curl per job, added for you. No agent to install.

Get a check for every job, on the same schedules and in your server's time zone. Or add checks one at a time.

Your crontab comes back with a ping on each job that reports its exit code, and each check lights up live when its first ping arrives. Not using cron? Copy a ready-made snippet for systemd, GitHub Actions, Kubernetes, Laravel, Python, Node.js or Ruby.

A missed run, a failure, an ERROR in the output, a run that overruns or one that's much slower than usual. By email, Slack, Discord, Teams or webhook.

Step-by-step guides: crontab · Kubernetes CronJobs · GitHub Actions · systemd timers · Laravel scheduler · Python · Node.js · Ruby and Rails

every night at 02:00, reporting the exit code

0 2 * * * /usr/local/bin/backup.sh;
curl -fsS https://cronomonitor.com/api/ping/<check-id>/$?

Why switch?

Unlimited checks on every plan, instead of paying per monitor.

1 page

Monthly price for 100 checks and one user on the cheapest plan that covers them, from each provider's public pricing page in October 2026, in the currency they list. Plans change, so check their sites for current details.

Unlimited checks on both plans. 14-day free trial with every Team feature, no card required.

Unlimited checks, with every monitoring feature

Up to 5 people

Ping log: last 100 pings per check, kept 30 days

Email, Slack, Discord, Teams + webhook alerts

Start free trial

Team

Unlimited checks, with every monitoring feature

Up to 15 people

Ping log: last 1,000 pings per check, kept a year

Email, Slack, Discord, Teams + webhook alerts

REST API and API keys

Audit log of every change

Start free trial

Every plan includes

Monitoring

Cron schedules in any time zone, or simple intervals

Import your whole crontab in one paste

Copy-paste setup for systemd, GitHub Actions, Kubernetes, Laravel and more

A ping log with each run's output, plus run-time charts

Maintenance windows, one-off or every week, that pause alerts and don't count against uptime

Guided setup: send a test ping and watch your first check go green

Alerts

Instant alerts when a job fails, logs an error, runs too long or slows down

Email, Slack, Discord, Teams + webhook alerts, set once per project

Alert only after repeated failures, with reminders while a job stays down

Reporting and teams

A status page for every project, with 30-day uptime

Notes on each incident, shown on your status page

A Monday report of uptime, failures and jobs getting slower

Monthly uptime reports to print or save as PDF for clients and managers

Your incident history as a CSV, ready for a spreadsheet

Status badges for your READMEs and wikis

Security and privacy

Nothing to install: jobs send an outbound HTTPS request, so nothing needs access to your servers

Encrypted connections everywhere (HTTPS, with HSTS)

Two-factor sign-in with an authenticator app, plus recovery codes

Passwords stored only as salted hashes; changing yours signs out every other device

Ping URLs are secret, and status badges use a separate token so they never reveal one

Payments handled by Paddle, our merchant of record; we never see your card details

Export or delete your data at any time

More detail in our privacy policy.

Create a check, then add a ping to the end of the job's line in your crontab. Cronomonitor expects that ping on the job's schedule and alerts you if it doesn't arrive.

0 3 * * * /usr/local/bin/backup.sh; curl -fsS https://cronomonitor.com/api/ping/<check-id>/$?

Do I need to install an agent or change my code?

No. A job only needs to make an HTTP request to its check's URL when it finishes, usually with curl, so it works anywhere that can reach the internet: servers, containers, CI pipelines and serverless functions.

Report the job's exit code by ending the ping URL with $? in your crontab: 0 counts as a success and anything else as a failure, which alerts you straight away. You can also call the URL with /fail on the end.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →