Knowing when something breaks: uptime checks, logs, metrics and traces, SLOs and error budgets, and incident response.
Logs, metrics and traces answer different questions about a running system. How each works, how trace IDs connect them, and what each costs to collect and keep.
SLIs, SLOs and SLAs defined with examples, how to pick an SLI, error budget math (99.9% over 30 days allows 43.2 minutes) and what an SLA adds.
How to run an incident from detection to review: severity levels, the incident commander and other roles, updates for users, timelines and blameless follow-ups.
Try what these guides describe on your own URLs, domains, code or files.