How does Relen Heartbeat / Cron Job monitoring work?

When you create a Heartbeat monitor, Relen gives you a unique webhook ping URL. Append a simple cURL command (`curl -m 10 https://api.relen.site/ping/YOUR_ID`) to the end of your cron script or background job. If the ping does not arrive within your grace period, Relen alerts you instantly.

Can we monitor TCP ports, DNS records, or ICMP pings in addition to HTTP?

Yes. Relen supports 13 check types including HTTP/HTTPS, TCP Port reachability, DNS record resolution, SSL/TLS certificate chains, and Heartbeat monitors.

How does Relen handle escalation routing and PagerDuty integration?

Relen integrates natively with PagerDuty Events API v2, Slack webhooks, Discord, Microsoft Teams, and custom webhooks. You can assign different notification channels to specific monitors or severity thresholds.

Can we automate monitor creation via CI/CD pipelines or Infrastructure as Code?

Yes. Relen provides a clean REST API authenticated with Bearer tokens so you can programmatically provision monitors during Terraform or GitHub Actions deployments.

For DevOps engineers, SREs & backend architecture teams

Catch silent cron job & webhook failures.

Monitor scheduled background workers, TCP ports, DNS records, and API endpoints. Instant alerts to PagerDuty and Slack — without alert fatigue.

Start 12-day free trial Explore check types

Single cURL ping setup13 check types includedPagerDuty & Slack integration5 global regions

The silent failure trap

Silent background failures are more dangerous than server crashes.

When a web server goes down, everybody sees it immediately. But when your nightly database backup job runs out of memory or a webhook queue listener locks up, your systems can stay degraded for weeks before discovery.

Scheduled database backups or billing cron jobs crash silently, leaving you blind until an audit or data loss event.
Webhook processing workers time out during high load without triggering standard HTTP 500 server alarms.
DNS configuration propagation errors or TCP port blocks lock users out while HTTP checks return stale cached responses.
Overly noisy alerting systems cause alert fatigue, leading engineers to mute Slack channels and miss real outages.

crontab — heartbeat check-in

# Nightly Postgres Backup (Expect heartbeat every 24h)

0 2 * * * /usr/bin/pg_dump db | gzip > /backup/db.gz && curl -m 10 https://api.relen.site/ping/hb_9f8a2b

✓ Heartbeat: Nightly Database BackupCHECKED IN (02:04 UTC)

✓ TCP Port: Redis Cache Cluster (:6379)REACHABLE (4ms)

⚠ Webhook Queue Worker Check-inMISSED · PAGERDUTY ALERTED

Built for SREs who value signal over noise

Robust infrastructure monitors designed to integrate cleanly with your existing alerting stack.

Zero-Overhead Cron Heartbeats

Add a single cURL ping to your crontab or background worker. Get paged immediately if a job misses its check-in.

TCP, DNS & Network Checks

Verify database ports, mail server reachability, and DNS record consistency across 5 geographic regions.

Noisy-Alert Suppression

Multi-region consensus verification ensures you only get woken up for confirmed, real-world infrastructure failures.

Developer-First REST API

Manage monitors, retrieve check histories, and automate status pages using clean REST endpoints and API keys.

DevOps & SRE monitoring — frequently asked questions

How does Relen Heartbeat / Cron Job monitoring work?: When you create a Heartbeat monitor, Relen gives you a unique webhook ping URL. Append a simple cURL command (`curl -m 10 https://api.relen.site/ping/YOUR_ID`) to the end of your cron script or background job. If the ping does not arrive within your grace period, Relen alerts you instantly.
Can we monitor TCP ports, DNS records, or ICMP pings in addition to HTTP?: Yes. Relen supports 13 check types including HTTP/HTTPS, TCP Port reachability, DNS record resolution, SSL/TLS certificate chains, and Heartbeat monitors.
How does Relen handle escalation routing and PagerDuty integration?: Relen integrates natively with PagerDuty Events API v2, Slack webhooks, Discord, Microsoft Teams, and custom webhooks. You can assign different notification channels to specific monitors or severity thresholds.
Can we automate monitor creation via CI/CD pipelines or Infrastructure as Code?: Yes. Relen provides a clean REST API authenticated with Bearer tokens so you can programmatically provision monitors during Terraform or GitHub Actions deployments.

Monitor your cron jobs & infrastructure free for 12 days

Create your account and add your first Heartbeat or API monitor in under two minutes.

Get started free See alerting docs