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.
URL: https://apievangelist.com
Run: Capabilities Using Naftiko
- SRE, Reliability, SLO, Chaos Engineering, Incident Response, Error Budget, On-Call, Resilience
- Created: 2026-05-19
- Modified: 2026-05-19
- Portal
- GitHubOrganization
- JSONSchema - SLO Schema
- JSONSchema - Chaos Experiment Schema
- JSON-LD
- Vocabulary
| Name | Description |
|---|---|
| Service Level Objectives and Error Budgets | Reliability platforms let teams define SLIs, set SLOs, and track error budgets to balance reliability work against feature delivery. |
| Chaos Engineering and Fault Injection | Chaos tools deliberately inject failures into systems to validate resilience and uncover hidden weaknesses before they cause incidents. |
| Incident Response and On-Call Orchestration | Platforms orchestrate on-call rotations, alert routing, escalation policies, and incident war rooms across distributed teams. |
| Runbook Automation and Response Workflows | Reliability platforms automate runbooks that trigger on incidents, capture context, and guide responders through remediation. |
| Blast Radius Reduction and Safety Controls | Chaos and incident tools include halt conditions, scope limits, and automated rollback to contain the blast radius of experiments and incidents. |
| Blameless Post-Incident Reviews | Platforms structure post-incident analysis to extract learning, capturing timelines, contributing factors, and follow-up actions. |
| Service Standards and Reliability Scoring | Internal developer platforms score services against reliability standards such as ownership, on-call coverage, SLO adoption, and runbook completeness. |
| Status Pages and Customer Communication | Status page platforms communicate incident state and maintenance windows to customers and stakeholders in real time. |
| Name | Description |
|---|---|
| SLO-Based Alerting | Replace threshold alerts with SLO burn-rate alerts that fire only when error budget is being consumed faster than sustainable. |
| Pre-Production Resilience Testing | Teams inject faults in staging environments to validate retries, timeouts, circuit breakers, and failover before production deploys. |
| Game Days and Continuous Verification | SRE teams run scheduled game days and continuous chaos experiments to verify runbooks, alerting, and failover behavior still work. |
| Incident Coordination at Scale | Platforms coordinate large incidents across multiple teams with auto-created channels, scribes, roles, and timeline capture. |
| Error Budget Policy Enforcement | When a service exhausts its error budget, policies can freeze deploys, page leadership, or trigger reliability investment. |
| On-Call Schedule Management | Manage rotation schedules, overrides, and escalation policies across global teams with chat and ticketing integrations. |
| Service Catalog and Reliability Standards | Track service ownership, tier, and adherence to reliability standards across the organization. |
| Customer-Facing Status Communication | Publish incident updates, scheduled maintenance, and component health to customers and subscribers. |
| Name | Description |
|---|---|
| Nobl9 | SLO platform that consolidates SLIs from observability sources into managed objectives with error budget tracking. |
| Gremlin | Chaos engineering platform for safely injecting CPU, memory, network, and dependency failures with built-in halt conditions. |
| PagerDuty | Incident response and on-call platform with rotation scheduling, escalation, event intelligence, and broad integrations. |
| Incident.io | Slack-native incident response platform that automates channel creation, roles, comms, and post-mortems. |
| FireHydrant | Incident management combining runbooks, retrospectives, status pages, and service catalog for reliability programs. |
| Chaos Mesh | Open-source CNCF chaos engineering platform for Kubernetes that injects pod, network, IO, and time faults. |
| OpsLevel | Internal developer portal that scores services against reliability standards such as SLOs, on-call, and runbooks. |
| Statuspage | Hosted status page platform for communicating incidents, maintenance, and component health to customers. |
Machine-readable API specifications organized by format.
- Reliability Vocabulary — Unified taxonomy mapping reliability resources, actions, workflows, and personas across SLO, chaos engineering, and incident response platforms
This index references the following reliability, chaos engineering, and incident response repositories:
- Amazon Fault Injection Simulator
- Better Stack
- Blameless
- Chaos Mesh
- Chronosphere
- Cortex
- FireHydrant
- Gremlin
- Harness
- Incident.io
- Lightstep
- Litmus
- Moogsoft
- Nobl9
- OneUptime
- OpsGenie
- OpsLevel
- PagerDuty
- Rootly
- SIGNL4
- Splunk On-Call (VictorOps)
- Squadcast
- Statuspage
- xMatters
- Zenduty
FN: Kin Lane
Email: kin@apievangelist.com