aid: reliability name: Reliability kind: topic description: >- An index and topic collection covering site reliability engineering (SRE), reliability platforms, service level objectives (SLOs), error budgets, chaos engineering, resilience testing, and incident response. Reliability platforms help teams define and measure reliability targets, intentionally inject failure to validate resilience, manage on-call rotations and alerting, coordinate incident response, and run blameless post-incident reviews. This collection includes SLO management platforms like Nobl9 and Chronosphere, chaos engineering tools like Gremlin, Chaos Mesh, Litmus, and AWS Fault Injection Simulator, internal developer platforms with reliability scoring like OpsLevel and Cortex, and incident response platforms like PagerDuty, OpsGenie, Incident.io, FireHydrant, Rootly, Blameless, Squadcast, and Zenduty. type: Index image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg tags: - SRE - Reliability - SLO - Chaos Engineering - Incident Response - Error Budget - On-Call - Resilience url: >- https://raw.githubusercontent.com/api-evangelist/reliability/refs/heads/main/apis.yml created: '2026-05-19' modified: '2026-05-19' specificationVersion: '0.19' apis: [] network: - name: Amazon Fault Injection Simulator url: https://raw.githubusercontent.com/api-evangelist/amazon-fault-injection-simulator/refs/heads/main/apis.yml - name: Better Stack url: https://raw.githubusercontent.com/api-evangelist/betterstack/refs/heads/main/apis.yml - name: Blameless url: https://raw.githubusercontent.com/api-evangelist/blameless/refs/heads/main/apis.yml - name: Chaos Mesh url: https://raw.githubusercontent.com/api-evangelist/chaos-mesh/refs/heads/main/apis.yml - name: Chronosphere url: https://raw.githubusercontent.com/api-evangelist/chronosphere/refs/heads/main/apis.yml - name: Cortex url: https://raw.githubusercontent.com/api-evangelist/cortex/refs/heads/main/apis.yml - name: FireHydrant url: https://raw.githubusercontent.com/api-evangelist/firehydrant/refs/heads/main/apis.yml - name: Gremlin url: https://raw.githubusercontent.com/api-evangelist/gremlin/refs/heads/main/apis.yml - name: Harness url: https://raw.githubusercontent.com/api-evangelist/harness/refs/heads/main/apis.yml - name: Incident.io url: https://raw.githubusercontent.com/api-evangelist/incident-io/refs/heads/main/apis.yml - name: Lightstep url: https://raw.githubusercontent.com/api-evangelist/lightstep/refs/heads/main/apis.yml - name: Litmus url: https://raw.githubusercontent.com/api-evangelist/litmus/refs/heads/main/apis.yml - name: Moogsoft url: https://raw.githubusercontent.com/api-evangelist/moogsoft/refs/heads/main/apis.yml - name: Nobl9 url: https://raw.githubusercontent.com/api-evangelist/nobl9/refs/heads/main/apis.yml - name: OneUptime url: https://raw.githubusercontent.com/api-evangelist/oneuptime/refs/heads/main/apis.yml - name: OpsGenie url: https://raw.githubusercontent.com/api-evangelist/opsgenie/refs/heads/main/apis.yml - name: OpsLevel url: https://raw.githubusercontent.com/api-evangelist/opslevel/refs/heads/main/apis.yml - name: PagerDuty url: https://raw.githubusercontent.com/api-evangelist/pagerduty/refs/heads/main/apis.yml - name: Rootly url: https://raw.githubusercontent.com/api-evangelist/rootly/refs/heads/main/apis.yml - name: SIGNL4 url: https://raw.githubusercontent.com/api-evangelist/signl4/refs/heads/main/apis.yml - name: Splunk On-Call (VictorOps) url: https://raw.githubusercontent.com/api-evangelist/victorops/refs/heads/main/apis.yml - name: Squadcast url: https://raw.githubusercontent.com/api-evangelist/squadcast/refs/heads/main/apis.yml - name: Statuspage url: https://raw.githubusercontent.com/api-evangelist/statuspage/refs/heads/main/apis.yml - name: xMatters url: https://raw.githubusercontent.com/api-evangelist/xmatters/refs/heads/main/apis.yml - name: Zenduty url: https://raw.githubusercontent.com/api-evangelist/zenduty/refs/heads/main/apis.yml common: - type: Portal url: https://apievangelist.com - type: GitHubOrganization url: https://github.com/api-evangelist - type: Features data: - name: Service Level Objectives and Error Budgets description: Reliability platforms like Nobl9, Chronosphere, and OpenSLO let teams define service level indicators (SLIs), set service level objectives (SLOs), and track error budgets to balance reliability work against feature delivery. - name: Chaos Engineering and Fault Injection description: Chaos engineering tools like Gremlin, Chaos Mesh, Litmus, and AWS Fault Injection Simulator deliberately inject failures into systems to validate resilience and uncover hidden weaknesses before they cause incidents. - name: Incident Response and On-Call Orchestration description: Incident response platforms like PagerDuty, OpsGenie, Incident.io, FireHydrant, and Rootly orchestrate on-call rotations, alert routing, escalation policies, and incident war rooms across distributed teams. - name: Runbook Automation and Response Workflows description: Reliability platforms automate runbooks and response workflows that trigger on incidents, capture context from connected systems, and guide responders through remediation steps. - name: Blast Radius Reduction and Safety Controls description: Chaos and incident tools include safeguards such as halt conditions, scope limits, and automated rollback to contain the blast radius of experiments and incidents. - name: Blameless Post-Incident Reviews description: Platforms like Blameless, Jeli, and FireHydrant structure post-incident analysis to extract learning without assigning blame, capturing timelines, contributing factors, and follow-up actions. - name: Service Standards and Reliability Scoring description: Internal developer platforms like OpsLevel and Cortex score services against reliability standards such as ownership, on-call coverage, SLO adoption, and runbook completeness. - name: Status Pages and Customer Communication description: Status page platforms like Statuspage, Better Stack, and OneUptime communicate incident state and maintenance windows to customers and stakeholders in real time. - type: UseCases data: - name: SLO-Based Alerting description: Replace threshold alerts with SLO burn-rate alerts that fire only when error budget is being consumed faster than sustainable, reducing alert fatigue while preserving signal. - name: Pre-Production Resilience Testing description: Teams use Gremlin, Chaos Mesh, or AWS Fault Injection Simulator in staging environments to validate retries, timeouts, circuit breakers, and failover before production deploys. - name: Game Days and Continuous Verification description: SRE teams run scheduled game days and continuous chaos experiments to verify that documented runbooks, alerting, and failover behavior still work as systems evolve. - name: Incident Coordination at Scale description: PagerDuty, Incident.io, and FireHydrant coordinate large incidents across multiple teams with auto-created Slack channels, scribes, roles, and timeline capture. - name: Error Budget Policy Enforcement description: When a service exhausts its error budget, automated policies in Nobl9 or Chronosphere can freeze deploys, page leadership, or trigger reliability investment until the budget recovers. - name: On-Call Schedule Management description: Platforms like PagerDuty, OpsGenie, and Squadcast manage rotation schedules, overrides, and escalation policies across global teams, with integrations into chat and ticketing tools. - name: Service Catalog and Reliability Standards description: OpsLevel, Cortex, and Backstage track service ownership, tier, and adherence to reliability standards like SLO coverage, on-call defined, and runbooks linked. - name: Customer-Facing Status Communication description: Statuspage, Better Stack, and OneUptime provide hosted status pages that publish incident updates, scheduled maintenance, and component health to customers and subscribers. - type: Integrations data: - name: Nobl9 description: SLO platform that consolidates SLIs from Prometheus, Datadog, New Relic, and other observability sources into managed service level objectives with error budget tracking. - name: Gremlin description: Chaos engineering platform for safely injecting CPU, memory, network, and dependency failures into production and staging systems with built-in halt conditions. - name: PagerDuty description: Incident response and on-call platform with rotation scheduling, escalation policies, event intelligence, and a broad integration ecosystem. - name: Incident.io description: Slack-native incident response platform that automates channel creation, roles, comms, and post-mortems for engineering teams. - name: FireHydrant description: Incident management platform combining runbooks, retrospectives, status pages, and service catalog for reliability programs. - name: Chaos Mesh description: Open-source CNCF chaos engineering platform for Kubernetes that injects pod, network, IO, and time faults via custom resources. - name: OpsLevel description: Internal developer portal that tracks service ownership and scores services against reliability standards such as SLOs defined, on-call set, and runbooks linked. - name: Statuspage description: Hosted status page platform from Atlassian for communicating incidents, maintenance, and component health to customers. maintainers: - FN: Kin Lane email: kin@apievangelist.com humanURL: https://apievangelist.com