Go in DevOps Panel
summary
Panel covers concrete practices and tradeoffs: use SLOs and error budgets (example cited as 99.999 SLO), reduce noisy alerts by investing in meaningful thresholds or an “alert-of-alerts” fallback, and prefer single-binary Go tools (Terraform, Prometheus) for easier ops. Proposals include propagate trace headers in net/http and richer execution-tracing hooks so OTel can collect telemetry without app code changes. Also: blameless postmortems, measure time-to-resolution, and accept that scale dictates whether teams run or hand off services.
AI-written summary · about
chapters (11)
- 0:00Panelist introductions
- 2:52What is DevOps?
- 7:33DevOps culture & practices
- 10:01Developers vs. SREs
- 13:51Alert management & monitoring
- 16:22Error budgets & innovation
- 20:40Blameless postmortems
- 23:33Bottom-up DevOps adoption
- 28:29DORA metrics
- 29:53Go in DevOps
- 34:11Q&A
related talks
39mShifting Left on Production Excellence with Observability
47mDevOps is for Product Engineers, too.
54mUnraveling the Differences
58mCultivating Production Excellence
32mDistributed DevOps
20mUsing Monitoring to Speed Up Your DevOps Journey
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
36mThe road to world-class observability