Status pages & incident communication — found from sitemap — Checkly

Cited by

Facts read from this source

• Status page purpose Report an error

  “Create status pages to communicate service health, incidents, and maintenance to your customers, with automated incidents and custom branding.”

• Status history days Report an error

  “A status page shows the current status and 90-day history of each component, plus open incidents and planned maintenance.”

• V2 deprecated Report an error

  “Older pages built from cards and services are deprecated but keep working — see Status pages v2 (deprecated).”

• Component types Report an error

  “Service: a monitored thing with its own status and uptime history. Group: a container that nests services under a shared heading. A group shows the average uptime of its children.”

• Component management Report an error

  “You manage them in the page’s settings, where you can add, nest, reorder, hide, and delete them. For each component you can also hide its historical data, which is shown by default, and you can show a group expanded when the page loads. Groups are collapsed by default, and a group needs at least one component.”

• Component statuses Report an error

  “Status Meaning Uptime calculation Operational Everything works N/A Under maintenance Planned maintenance is running 0% Degraded performance Slow, but working 0% Partial outage Some functionality is unavailable 30% Major outage The component is down 100%”

• Header worst status Report an error

  “The page header shows the worst status across all components.”

• Automation rules Report an error

  “Automation rules open and resolve incidents based on your checks. A rule matches failing checks by tag: when a check carrying one of the rule’s tags fails, Checkly opens one incident impacting the components the rule lists, and resolves it when the check recovers.”

• Automation plan availability Report an error

  “Incident automation is available on Team and Enterprise plans. View pricing”

• Uptime formula Report an error

  “Uptime is calculated over the last 90 days, per component, from incident impacts: Major outage counts as 100% downtime. Partial outage counts as 30% downtime. Degraded performance counts as 0% downtime as the service is still usable. Under maintenance counts as 0% downtime as it is an intentional pause of service. Uptime = ((Total time - Weighted downtime) / Total time) × 100”

• Uptime incident driven Report an error

  “Uptime is driven by incidents, not directly by check results: without an automation rule or a manually created incident, a failing check does not lower uptime.”

• Cli management Report an error

  “Status pages, components, and automation rules can be fully managed with the Checkly CLI. See the StatusPageV3 construct. checkly import status-page:<id> imports an existing page with its components and rules into your project.”

• Terraform resources Report an error

  “With Terraform, use the checkly_status_page_v3, checkly_status_page_v3_component, and checkly_status_page_v3_automation_rule resources.”

Scores citing this record

• The Agency Developer Status pages & incident communication
• The Customer Support Lead Status pages & incident communication
• The Customer Support Lead API, monitoring as code & team administration
• The E-Commerce Operations Manager Status pages & incident communication
• The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
• The SaaS Platform Engineer Status pages & incident communication
• The SaaS Platform Engineer API, monitoring as code & team administration
• The Information Security Officer Status pages & incident communication
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Skeptic Status pages & incident communication