Operations

This section covers the operational aspects of running Rack Gateway in production, including monitoring, maintenance, upgrades, and troubleshooting.

Operational Areas

Monitoring Health checks, metrics, and error tracking with Sentry.

Database Maintenance Migrations, backups, and data management.

Troubleshooting Common issues and how to resolve them.

Upgrades Upgrading Rack Gateway to new versions.

Quick Reference

Health Endpoints

Endpoint	Purpose	Expected Response
/api/v1/health	Liveness check	{"status": "ok"}
/api/v1/health/ready	Readiness check	{"status": "ready", "database": "connected"}

Common Commands

# Check gateway health
curl https://gateway.example.com/api/v1/health

# View recent audit logs (admin)
rack-gateway admin audit list --limit 50

# Check database connectivity
rack-gateway migrate --dry-run

Log Locations

Deployment	Log Location
Docker	docker logs rack-gateway
Convox	convox logs -a rack-gateway
Kubernetes	kubectl logs -l app=rack-gateway

Operational Runbooks

Daily Checks

1. Verify health endpoints respond correctly
2. Check error tracking (Sentry) for new issues
3. Review audit logs for unusual activity

Weekly Tasks

1. Review user access patterns
2. Check for unused API tokens
3. Verify backup integrity

Monthly Tasks

1. Rotate API tokens as needed
2. Review RBAC role assignments
3. Check for available updates

Tip

Automate these checks where possible. Use monitoring tools to alert on health endpoint failures and error spikes.

Emergency Procedures

Gateway Unreachable

1. Check health endpoints
2. Verify database connectivity
3. Check container/pod status
4. Review recent deployments or changes

Suspected Security Incident

1. Do not modify audit logs
2. Check audit log for suspicious activity
3. Review active sessions and API tokens
4. Contact security team
5. Preserve evidence for forensics

Database Issues

1. Check database connectivity from gateway
2. Verify database is accepting connections
3. Check for blocking queries or locks
4. Review recent migrations

See Troubleshooting for detailed procedures.