Playbooks & production notes
Stability, page 2
Reliability practices for finding silent failures, handling third-party errors, keeping useful logs, and recovering an AI-built app.
Stability
What is graceful degradation? Keeping the rest of the app usable when one provider is down
Stability
AWS logging and monitoring for a small app: CloudWatch logs, custom metrics, CloudTrail, and the alarms worth the bill
Stability
How long to keep application logs: a retention window you can show, and what it costs to keep more
Stability
How to alert on error rate spikes, latency, connection pressure, queue backlog and spend
Stability
How to build an ops dashboard: uptime, errors, latency, signups and revenue in a single view
Stability
Logs severity levels in production: debug, info, warn, error, and what stays switched on
Stability
No idea where users drop off: the four product events to instrument, and how to prove they fire
Stability
OpenTelemetry distributed tracing: what it replaces, what it costs to adopt, and when to skip it
Stability
Pino logging in a Node app: the setup, the levels, and when winston or morgan is the better fit
Stability
Slack alerting someone actually acts on: where alerts go, who is on call, and how to tune out the noise
Stability
What a trace ID is, and how trace IDs and correlation IDs follow one request across your app
Stability
Cron every minutes, from 1 to 30: the line, where the scheduled job actually runs, and how you know it ran
Stability
Docker Compose health check and restart policies: telling the platform when a container is actually ready
Stability
Hardening SaaS applications resilience: the ten reliability checks for an AI-built app
Stability
How to set a timeout on fetch, and on every other external call: AI, email, payments and the database
Stability
Incident response plan template for a team of five: a security incident response template you can fill in today
Stability
The RCA meaning software teams use: root cause analysis after an outage, and the postmortem that makes the fix stick
Stability