Features page (alerting) — Checkly

Cited by

Facts read from this source

• Retry strategies Report an error

  “Retry every failure with fixed, linear, or exponential backoff, from the same region or a different one”

• Escalation policies Report an error

  “Alert on the first failed run, the third, or after five minutes of sustained failure. Reminders re-send on your cadence until the check recovers.”

• Alert routing scope Report an error

  “Account-wide defaults, overridden per group or per check.”

• Alert types Report an error

  “Each channel subscribes to exactly the alert types it should carry: failure, degradation, recovery, or SSL expiry.”

• Alerting as code Report an error

  “They're TypeScript constructs in your repo: reviewed like code, deployed with your checks, and identical across every environment.”

• Slack Report an error

  “Slack Rich alerts in any channel, with failure context and a link to the result.”

• Pagerduty Report an error

  “PagerDuty Trigger and auto-resolve incidents on your existing escalation policies.”

• Opsgenie Report an error

  “Opsgenie Open alerts with priorities mapped to your on-call rotations.”

• Microsoft teams Report an error

  “Microsoft Teams Post alerts to team channels through incoming webhooks.”

• Sms Report an error

  “SMS Text the on-call phone directly. No app or wifi required.”

• Incident io Report an error

  “incident.io Kick off incident workflows straight from a failed check.”

• Rootly Report an error

  “Rootly Create and resolve Rootly incidents automatically.”

• Firehydrant Report an error

  “FireHydrant Turn confirmed failures into FireHydrant incidents.”

• Discord Report an error

  “Discord Alert your team server the moment a check fails.”

• Telegram Report an error

  “Telegram Push alerts to private chats or group channels via bot.”

• Additional channels Report an error

  “Also speaks GitLab Alerts, ilert, Spike.sh, Splunk On-Call, and StatusPage. That's 18+ channels, each with its own alert-type filters.”

• Webhooks Report an error

  “Webhooks give you the raw pipe: any URL, any method, any payload.”

• Webhook variables Report an error

  “Inject {{ALERT_TITLE}}, {{CHECK_NAME}}, {{RESULT_LINK}}, and more”

• Webhook secrets Report an error

  “Reference secrets with {{VARIABLE}} syntax, so nothing is hardcoded”

• Reminder intervals Report an error

  “Both support reminders, re-sent at 5, 10, 15, or 30 minute intervals up to a cap you set, and both stop automatically the moment the check recovers.”

• Multi location threshold Report an error

  “For checks running in parallel across locations, you can also require a percentage of locations to fail before alerting.”

• Ssl expiry threshold Report an error

  “Each channel independently subscribes to failures, degradations, recoveries, and SSL certificate expirations (with a configurable day threshold).”

• Terraform provider Report an error

  “Prefer clicks? Everything has full parity in the web app, and there is a Terraform provider too.”

• Cli constructs Report an error

  “Alert channels, retry strategies, and escalation policies are all TypeScript constructs in the Checkly CLI”

• Escalation run based definition Report an error

  “Run-based escalation alerts after N consecutive failed runs; time-based escalation alerts after a check has been failing for N minutes.”

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 Alerting, escalation & on-call
• The Customer Support Lead Alerting, escalation & on-call
• The E-Commerce Operations Manager Alerting, escalation & on-call
• The SaaS Platform Engineer Alerting, escalation & on-call
• The Information Security Officer Alerting, escalation & on-call
• The Skeptic Alerting, escalation & on-call