What are Post-Mortem and Blameless Culture?

Question

Accepted Answer

**Post-Mortem** — incident analysis. **Blameless Culture** — focus on systems, not people.

**Template:**
```markdown
# Post-Mortem: API Outage
- SEV: SEV1
- Duration: 45 minutes
- Impact: 100% of users

## Timeline
| Time | Event |
|-------|---------|
| 14:00 | Alert: High error rate |
| 14:05 | Investigation |
| 14:15 | Redis issue |
| 14:25 | Redis restart |
| 14:30 | Recovery |

## Root Cause
Redis OOM due to insufficient memory limit.

## Action Items
| # | Action | Owner | Deadline |
|---|---------|---------------|--------|
| 1 | Memory monitoring | @ivan | 2024-01-20 |
| 2 | Update runbook | @petr | 2024-01-22 |
```

**Blameless vs Blameful:**
- Blameful: "Ivan made a mistake."
- Blameless: "Config failed validation. Automatic validation is needed."

DevOps: What are Post-Mortem and Blameless Culture?