Alerting, escalation & on-call — found from sitemap — Cronitor

Cited by

Facts read from this source

• Alert triggers Report an error

  “Alerts are the notifications Cronitor sends when a monitor fails or an assertion is violated. Recovery alerts are also sent when a monitor returns to a "healthy" state.”

• Alert contents Report an error

  “Issue context - Direct link to the open issue with full details Monitor information - Which specific monitor failed and error details Failure description - What went wrong and when it happened Recovery status - Whether the issue is ongoing or resolved Action links - Quick access to pause alerts, view history, or manage the monitor”

• Issues Report an error

  “Issues are Cronitor's incident management hub - they help your team coordinate response when monitors fail - issues automatically open when monitors fail and close when they recover, creating a complete incident timeline”

• Issues features Report an error

  “Status page publishing - One-click sharing to keep customers informed during outages Persistent tracking - Issues remain accessible for post-incident review and documentation Severity management - Categorize impact level and assign ownership to team members”

• Notification lists recipients Report an error

  “Email addresses - Send detailed alerts to any email SMS numbers - Text message alerts for urgent issues Alert integrations - Slack, PagerDuty, Teams, Discord, and more”

• Default notification list Report an error

  “All accounts have a default notification list. When an account is created, this list initially contains the signup user's email address. If a monitor's notify field is omitted or empty, Cronitor uses this list.”

• Slack Report an error

  “Slack Send alerts to channels or direct messages with rich formatting and action buttons”

• Microsoft teams Report an error

  “Microsoft Teams Deliver alerts to Teams channels with embedded monitor details and quick actions”

• Discord Report an error

  “Discord Post formatted alerts to Discord servers with customizable webhooks”

• Google chat Report an error

  “Google Chat Send alerts to Google Workspace Chat spaces using webhooks”

• Telegram Report an error

  “Telegram Receive alerts via Telegram bot in direct messages or group chats”

• Lark Report an error

  “Lark Deliver alerts to LarkSuite channels using custom bot integrations”

• Pagerduty Report an error

  “PagerDuty Create incidents with automatic escalation, on-call routing, and resolution tracking”

• Datadog on call Report an error

  “Datadog On-Call Route Cronitor alerts to a Datadog On-Call team for escalation and incident response”

• Opsgenie Report an error

  “OpsGenie Trigger OpsGenie alerts with intelligent routing and escalation policies”

• Splunk on call Report an error

  “Splunk On-Call Route alerts through Splunk On-Call with timeline integration and team coordination”

• Webhooks Report an error

  “Webhooks Send custom HTTP requests to any endpoint with flexible payload formatting”

• Notification list environments Report an error

  “Choose which environments the list should be active in”

• Test alerts Report an error

  “Add ?state=fail to the end of the telemetry URL and hit enter.”

• API resources Report an error

  “Issues API - Create, update, and retrieve issues Notification Lists API - Manage notification lists Monitor API - Configure alert preferences for monitors”

• Mcp server Report an error

  “Coding agents can manage notification lists and investigate issues through the Cronitor MCP server”

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