Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Observability for Go is a first-class interview topic at SRE-heavy companies. This module covers structured logging in Go (log/slog introduced in Go 1.21 — the standard library logger that finally does structured JSON output, slog.Logger, LogAttrs, the Handler interface), contextual logging (propagating a logger or trace ID through context.Context), OpenTelemetry SDK for Go (tracing with otel.Tracer, spans, attributes, the OTLP exporter — instrumenting a gin or net/http server, a gRPC client, a database query), the prometheus/client_golang library (Counter, Gauge, Histogram, Summary — the /metrics handler, custom metric registration, the four golden signals applied to a Go service), pprof in production (the net/http/pprof package, the go tool pprof flame graph, the expvar package for live Go metrics), and the scenario question that comes up at every SRE-leaning company: 'your Go service's p99 latency spiked — walk me through the investigation starting from your observability stack.'
Full catalog
Topics are ordered for learning. Within each topic, rows are numbered 1–0 globally so you always know where you are. Collapse topics if you want a lighter view — use Expand all when you need the full list again.
Numbers 1–0 follow the order we recommend — click any row to open the full answer, or use the sticky Next link at the bottom of each page to go Q1 → Q0.