---
since: 1.2.1
---

# Runbook — Production Incident

## First Response

1. Identify the failing surface.
2. Check service status.
3. Check recent logs.
4. Check CPU/RAM/disk.
5. Check PostgreSQL.
6. Check Redis.
7. Check Cloudflare.
8. Check the most recent deployment.

## Service Checks

```bash
sudo systemctl status djangoplay
sudo systemctl status djangoplay-celery
sudo systemctl status postgresql
sudo systemctl status redis-server
```

## Resource Checks

```bash
free -h
df -h
uptime
```

## Logs

```bash
sudo journalctl -u djangoplay -n 200 --no-pager
sudo journalctl -u djangoplay-celery -n 200 --no-pager
```

## Rule

Do not make several unrelated changes at once. Establish the failure boundary first.