Features page (cron job monitoring) — Cronitor

Cited by

Facts read from this source

• Alert types Report an error

  “Get an alert when a job fails, starts late, or never starts.”

• Slow job alerts Report an error

  “Slow-job alerts with per-job thresholds, grace periods and failure tolerance.”

• Log capture Report an error

  “Cronitor captures stdout and stderr as the job runs and keeps them with that execution — no SSH, grep, or timestamp matching.”

• Metrics Report an error

  “It also records success rate, duration, and custom metrics, so you can investigate today or compare trends months later.”

• Retention Report an error

  “12 months of retention — compare this run to the last one that worked.”

• Cli setup Report an error

  “The Cronitor CLI reads your crontab — or Windows Task Scheduler — and walks through each job with you.”

• Cli wrapper Report an error

  “0 9 * * * cronitor exec send-invoices "/usr/local/bin/send-invoices.sh"”

• Sdk Report an error

  “Use an open-source SDK for tools such as Java, Airflow, and GitHub Actions, or send events directly to the telemetry API.”

• Environments Report an error

  “crontab kubernetes windows docker python celery node ruby sidekiq php laravel http api”

• Instrument sources Report an error

  “Register cron, Kubernetes CronJobs, Sidekiq, Celery, Windows Task Scheduler — or anything that can make an HTTP request.”

• Missed run detection Report an error

  “Cronitor holds your schedule and expects each run. Miss the window and it alerts — absence is a failure here, not silence.”

• Duration alerting Report an error

  “Every duration is compared with that job's own history. Use the automatic slow-job alert, or set your own threshold and watch p95 instead of averages.”

• Alert routing Report an error

  “Page on the third consecutive miss instead of the first flake, and send it to Slack or PagerDuty.”

• Alert channels faq Report an error

  “Cronitor triggers an alert to email, Slack, PagerDuty, or any other channel you configure.”

• Platform modules Report an error

  “01 Jobs Monitor cron jobs and scheduled agents. 02 Checks Check uptime, performance, and SSL. 03 Heartbeats Monitor any source with a heartbeat. 04 Status Pages Share uptime on a public or private status page. 05 Analytics Track website traffic, errors, and performance.”

• Shared dashboard Report an error

  “They all share one dashboard and alert pipeline, so a late job and a down endpoint reach the same on-call team.”

• Agent monitoring Report an error

  “Cronitor records when Codex, Claude Code, or another agent starts, completes, or fails and alerts you when the cron-driven run is missing.”

• Custom metric telemetry Report an error

  “Telemetry can also carry custom metrics, such as tokens or cost, as metric=name:value parameters. Cronitor charts them and alerts you when a value breaks an assertion.”

• No code change Report an error

  “No code changes are required. Wrapping the command in your crontab with cronitor exec is a one-line change per job and captures start, completion, exit status, and output automatically.”

• Log search Report an error

  “Logs attached to the execution that wrote them, searchable per run.”

• Dashboards Report an error

  “Success rate, duration percentiles and custom metrics on realtime dashboards.”

• Developer talk Report an error

  “Talk to a Developer”

• Free start Report an error

  “Start for free”

• SAML SSO docs Report an error

  “Configure SAML SSO”

• API docs Report an error

  “API Docs”

Scores citing this record

• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Agency Developer Pricing transparency
• The SaaS Platform Engineer Alerting, escalation & on-call
• The Information Security Officer Pricing transparency