Features

Cron / Heartbeat monitoring

You send an HTTP POST with a JSON payload. We handle the rest.

• Three lifecycle states: run (job started), complete (success), fail (error). Plus optional skip (cycle intentionally skipped — e.g. weekend).
• Heartbeat-only mode. Skip run/complete — just have the job ping once every X seconds. No ping = alert.
• Expected interval + grace period. Tell us “this job runs hourly, 5 minute grace”. Cronitorex detects missed runs automatically.
• Duration tracking. Every complete ping carries a duration in seconds — spot slowdowns early.
• Exit code + stderr capture. With fail you can send exit_code and error_output (up to 64KB of stderr). The dashboard shows what blew up.
• Tags + project metadata. Group monitors. Multi-tenant via tags (great for agencies).
• State transitions audit. Every event has timestamp, host, source. CSV export, date filtering.

HTTP uptime checks

Our built-in scheduler hits your endpoints for you.

• Configurable interval. 30s / 60s / 5min / 15min / 1h (depends on plan).
• Expected status codes. Default 2xx-3xx. Require a specific 200 or a range like 200-299.
• Response time threshold. Alert when response time > N ms (for N consecutive checks).
• Retry logic. 3 attempts before flagging “down” (protects against flaky networks).
• Methods: GET, POST, HEAD. Custom headers, custom body, basic auth, bearer tokens.
• Body content assertion. “Response must contain string X” or “must not contain string Y”.
• Multi-region (planned). Today we probe from a single EU location; multi-region on the roadmap.

SSL certificate alerts

• Daily check of every monitored domain.
• Multi-stage warnings: 30 days / 14 days / 7 days / 1 day before expiry.
• Cert chain validation. Detects expired intermediate cert, mismatched CN.
• Wildcard support. *.cronitorex.com treated as its own check.
• Bypass warning for cert managers (Let’s Encrypt auto-renewal).

Alerts and integrations

Channel	Plan
Email	every plan
Webhook (custom HTTP POST)	Starter+
Slack	Pro+
PagerDuty	Business
Discord / Teams / Telegram	via webhook + your own bridge

• Alert routing. Per monitor + per tag + per project. Backup channel if primary fails.
• Quiet hours. Mute alerts on weekends / overnight (per channel).
• Grouped alerts. Multiple jobs failing at once? One message, not spam.
• Re-alerting. Repeat alert every X minutes until acknowledged.
• Resolved notifications. Notify when a monitor recovers to “ok”.

Dashboard

• Live event stream. Every ping visible within seconds of arrival.
• Timeline view. All monitors side-by-side, colour-coded by state.
• Failure analytics. Top failing monitors, average failure rate, time-of-day patterns.
• Slowest jobs. Duration histogram per monitor, p50 / p95 / p99.
• Health Map. Grid of every monitor — locate problems at a glance.
• Filters / search. By tag, project, host, date.

API

• REST + JSON. Single /ping endpoint, simple payload.
• Bearer token auth. API key per user, rotation from the panel.
• Rate limiting. Per-IP + per-user, fair use.
• Swagger UI + Postman collection. Interactive testing.
• GET pings. We accept GET pings via query params for legacy systems (cron, healthcheck.sh).

Data and privacy

• Storage: PostgreSQL on AWS EU infrastructure.
• History retention: 7 / 30 / 90 / 365 days depending on plan.
• API keys hashed in DB. Plaintext shown once, at generation time.
• Backups at-rest encrypted. Daily snapshots, 30 day retention.
• GDPR-compliant. Data export, account deletion on request.
• No self-hosting (by design). You pay us to run it — that’s our job.

Operations

• Service status page at status.cronitorex.com.
• 99.95% SLA on the Business plan.
• Maintenance windows announced 7 days in advance.

What we do NOT do (deliberately)

• Distributed tracing.
• APM / code-level metrics (Datadog APM tier).
• Application log aggregation.
• Mobile push (on the roadmap, not shipped).

Cronitorex does job status monitoring and uptime. Different tools for different needs.