Uptime reports, data & the vendor's own reliability — found from sitemap — openstatus

Cited by

Facts read from this source

• Incident auto creation threshold Report an error

  “An incident is created automatically when at least half of a monitor's configured regions report an error”

• Incident scope Report an error

  “An incident is scoped to a single monitor and is primarily an internal object”

• Incident auto resolve Report an error

  “It can be acknowledged (someone is on it) and resolved (it's over) — and openstatus auto-resolves it when checks recover.”

• Status report creation Report an error

  “It is created manually (dashboard, CLI, or API), belongs to a single status page, and is attached to one or more of that page's components”

• Status report update statuses Report an error

  “A status: investigating → identified → monitoring → resolved.”

• Status report component impacts Report an error

  “Each update can declare a per-component impact — degraded_performance, partial_outage, or major_outage — and operational once it recovers”

• Impact uptime weighting Report an error

  “a major outage counts fully against uptime, a partial outage counts half, and degraded performance not at all.”

• Declared incidents Report an error

  “With incident management, someone declares an incident by hand, from the dashboard or Slack. It carries a severity, a commander, an internal timeline and, once resolved, a postmortem.”

• Maintenance windows Report an error

  “A maintenance window is for disruption you know about in advance — a database upgrade, a migration, a deploy with expected downtime. Like a status report, it belongs to one status page and targets that page's components. Unlike a status report, it is scheduled: it has a from and a to”

• Maintenance uptime exclusion Report an error

  “It never counts against uptime. Uptime is computed from raw check results (or report impacts with the Reports only status source); a maintenance window only changes the displayed status.”

• Maintenance subscriber notification Report an error

  “Subscribers can be notified when it's scheduled, so the disruption is announced before it happens instead of explained after.”

• Status page display precedence Report an error

  “an active incident (error) outranks an unresolved status report (degraded), which outranks maintenance (info), which outranks operational.”

• Uptime status sources Report an error

  “Impacts also weight the uptime percentage on status pages using the Reports only status source or Monitor checks with Time per status”

Scores citing this record

• The Agency Developer Alerting, escalation & on-call
• The Agency Developer Status pages & incident communication
• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Customer Support Lead Checks, locations & failure confirmation
• The Customer Support Lead Alerting, escalation & on-call
• The Customer Support Lead Status pages & incident communication
• The Customer Support Lead Uptime reports, data & the vendor's own reliability
• The E-Commerce Operations Manager Checks, locations & failure confirmation
• The E-Commerce Operations Manager Alerting, escalation & on-call
• 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 Checks, locations & failure confirmation
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Status pages & incident communication
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer Status pages & incident communication
• The Skeptic Alerting, escalation & on-call
• The Skeptic Uptime reports, data & the vendor's own reliability