Features page (heartbeat monitoring) — Cronitor

Cited by

Facts read from this source

• Heartbeat alert on missing Report an error

  “Alert on missing beats or unexpected metric values.”

• Heartbeat scope Report an error

  “Works for services, scripts, devices, and agents.”

• Custom metrics per beat limit Report an error

  “Up to 10 custom metrics on each beat, plus built-ins such as count and duration.”

• Custom metrics assertions Report an error

  “Alert on the latest value or on a window: metric.queue_depth.mean < 100 over 24 hours.”

• Custom metrics charting Report an error

  “Name each metric yourself. Cronitor charts the values over time.”

• Heartbeat transport Report an error

  “A heartbeat is a single HTTPS request from your code to a URL we hand you.”

• Heartbeat config methods Report an error

  “CONFIGURED BY dashboard · API · YAML”

• Heartbeat alert integrations count Report an error

  “ALERTS 10+ integrations”

• Retention Report an error

  “RETENTION 12 months”

• Grace period Report an error

  “starts a grace period the moment the next one is late.”

• No install required Report an error

  “No inbound network access or installed agent is required, so it works from locked-down hosts, containers, and edge devices.”

• Use case hosts Report an error

  “Monitor hosts Know when an internal host or container stops reporting, without exposing it to an uptime check.”

• Use case email Report an error

  “Monitor email campaigns Add Cronitor as a subscriber to any important mailing list and know instantly if email stops flowing.”

• Use case activity Report an error

  “Monitor user activity Send heartbeats on key system and application events and follow trends over time.”

• Use case scrapers Report an error

  “Monitor any scraper Include heartbeats in crawl maps and be alerted if ingestion or scraping activity stops.”

• Use case webhooks Report an error

  “Monitor webhooks Subscribe Cronitor to a webhook and get alerted when a third-party service stops sending events.”

• Use case devices Report an error

  “Monitor devices Send heartbeats from internet-connected devices and see which ones have stopped reporting.”

• Use case agents Report an error

  “Monitor agents NEW Every scheduled agent run can emit a heartbeat — know the moment your automations stop.”

• Live dashboards Report an error

  “Live dashboards See every heartbeat monitor and its current status on one live dashboard.”

• Scheduled reports Report an error

  “Scheduled reports Daily, weekly and monthly reporting for your whole team, so everybody stays informed.”

• Config as code Report an error

  “Configuration as code Provision and version-control monitors with YAML and the Cronitor CLI.”

• Open source sdks Report an error

  “Add monitoring to any codebase in minutes with one of our official, open source SDKs.”

• Check vs heartbeat Report an error

  “A CHECK Cronitor makes the request, on your schedule, from the regions you choose. It needs something reachable, and what it proves is that your endpoint answered correctly.”

• Platform monitors Report an error

  “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.”

• Uptime stat 12 months Report an error

  “99.997% UPTIME LAST 12 MONTHS”

• Scale events per day Report an error

  “100M+ EVENTS PER DAY”

• Scale checks per day Report an error

  “10M+ CHECKS PER DAY”

• Scale alerts per day Report an error

  “10K+ ALERTS PER DAY”

• Founded Report an error

  “2014 FOUNDED IN CALIFORNIA”

• Free tier signal Report an error

  “Start for free”

• Alert delivery Report an error

  “They arrive wherever your on-call rotation already lives.”

• Check regions selectable Report an error

  “Cronitor makes the request, on your schedule, from the regions you choose.”

• Alert email pagerduty examples Report an error

  “Email team: data-eng nightly-etl fell below its assertion threshold PagerDuty on-call: data-eng”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Agency Developer European sovereignty
• The Customer Support Lead Uptime reports, data & the vendor's own reliability
• The Customer Support Lead European sovereignty
• The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
• The E-Commerce Operations Manager European sovereignty
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The SaaS Platform Engineer European sovereignty
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer API, monitoring as code & team administration
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Information Security Officer European sovereignty
• The Skeptic Alerting, escalation & on-call
• The Skeptic Uptime reports, data & the vendor's own reliability
• The Skeptic European sovereignty