Skip to content

Observability

Logs, metrics, traces, and the art of debugging production.

logsmetricstracesOpenTelemetryPrometheusGrafanaDatadogSentryalerting

Lessons

  1. 16.1Logs, metrics and traces: the three pillars of observabilityWhen production breaks, you need clues. Metrics, traces and logs are three kinds of clues, and they work best together. 30 min Incident: checkout is slow Latency percentiles
  2. 16.2OpenTelemetry: instrumentation, context propagation and samplingA trace only helps if it follows the request everywhere. OpenTelemetry is the shared standard that makes that happen. 30 min Latency percentiles
  3. 16.3Incident response: alerts, on-call, mitigation and blameless postmortemsSomething is broken and users are waiting. Here's how good teams stay calm, fix it fast, and learn from it. 30 min Incident: checkout is slow

On the job: try it on your own project

Pick a recent bug or incident. Ask Claude Code to show you what logs, metrics and traces exist for that flow and what was missing to find the cause fast. Then review your alerts: which ones fire often and get ignored? Write a short observability gap list and one improvement, such as a missing trace or a noisy alert to remove.

Can you do this now?

0/4. Anything you can't tick yet: reopen that lesson's practice ladder.