Production
Monitoring, logging, error tracking, and what to do when things go wrong at 3am.
-
Read logs and trace an error
Where logs live once your app is deployed, how to follow a stack trace back to your own code, and what is worth writing to the log in the first place.
read -
Monitor your app and set useful alerts
An outside uptime check, a health endpoint that actually touches the database, and alerts tuned so you still believe them. The minimum monitoring for a first real deployment.
read -
Track errors in production
Why users never report crashes, and how an error tracker catches them anyway: a small SDK, source maps to decode minified stack traces, and triage by users affected instead of raw event count.
read -
Respond to a production incident
An incident playbook for a team of one: confirm the outage is real, roll back before you debug, find the change that caused it, and write three sentences so the next one hurts less.
read