NEW
The deliberate introduction of failures or adverse conditions to evaluate system resilience, recovery behavior, and observability.
DESCRIPTION
Fault injection tests how systems behave under controlled failures like latency, resource exhaustion, or service crashes. It helps validate resilience patterns, retry logic, and observability quality before incidents occur. Practices range from unit-level error simulation to production chaos experiments. Managed services like AWS FIS and Azure Chaos Studio orchestrate experiments safely. Well-designed experiments yield actionable improvements to reliability, incident response, and architecture.
ALTERNATIVE DEFINITIONS
Wikipedia
Fault injection is a software testing technique in which errors are deliberately introduced into a system to determine whether it can handle the error properly.
Focuses on testing technique and error handling verification.
AWS Fault Injection Simulator
AWS FIS is a managed service that helps you perform controlled fault injection experiments to improve an application’s performance, observability, and resilience.
Operational framing of fault injection within a managed cloud service.
Microsoft Azure Chaos Studio
Azure Chaos Studio enables fault injection and chaos engineering experiments to validate how applications respond to failures and improve reliability.
Highlights cloud-native orchestration of experiments and reliability improvements.
RELATED TERMS
Chaos Monkey Resilience Testing Load Testing Failure Modes Circuit Breaker Retry Policy Observability Postmortem GameDay
COMPETING TERMS
Chaos Engineering Stress Testing
KNOWLEDGE AREAS
Observability & Telemetry Testing & Validation Infrastructure Software Engineering
TARGET AUDIENCE
DevOps Engineer Software Architect Cloud Architect IT Manager Software Developer Solution Architect
EXTERNAL SOURCES
- Wikipedia - Fault injection
- AWS - Managed fault injection service overview
- Microsoft - Chaos Studio overview for fault injection
- Principles of Chaos - Foundational guidance for chaos experiments
TOP QUESTIONS
What is Fault Injection?
It deliberately introduces failures or adverse conditions to validate resilience, recovery, and observability in systems.
Category: Definition
How does Fault Injection differ from Chaos Engineering?
Fault injection focuses on specific faults; chaos engineering covers broader systemic experiments and hypotheses about complex behavior.
Category: Distinction
Why is Fault Injection valuable?
It reveals reliability weaknesses before incidents occur, guiding improvements in architecture, runbooks, and monitoring.
Category: Relevancy
What are common Fault Injection scenarios?
Network latency, instance termination, resource exhaustion, dependency failures, and API timeouts are typical experiments.
Category: Example
What are risks of Fault Injection?
Poorly scoped experiments can cause outages. Run in isolation, define abort conditions, and monitor closely.
Category: Risks
How do you design Fault Injection experiments?
Start with a hypothesis, define metrics and success criteria, limit blast radius, and document learnings in postmortems.
Category: Process
What tools support Fault Injection?
AWS FIS, Azure Chaos Studio, Gremlin, Chaos Mesh, and custom scripts enable controlled experiments.
Category: Tools
How to measure success in Fault Injection?
Track recovery time, error rates, SLO impacts, and detection speed; ensure automation improves these metrics over time.
Category: Testing
Where to begin with Fault Injection?
Start with staging environments, low-risk scenarios, and clear rollback plans; then gradually expand scope.
Category: Requirements