SIG Instrumentation Introduction and Deep Dive
summary
SIG Instrumentation enforces concrete changes: it replaces unstructured logs with structured logging completed for kubelet (v1.21) and kube-scheduler (v1.24) and adds contextual logging primitives in 1.24 so request-scoped key/value pairs travel through call chains. Tracing lands as alpha in the apiserver (v1.22) and requires an OpenTelemetry collector sidecar to export spans; kubelet and runtimes are adopting tracing next. Metrics get a stability framework and a metric-rewrite/killlist tool to prevent cardinality explosions and production OOMs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:55What do we do?
- 2:45How do we do it?
- 4:02Subprojects
- 5:37Metrics Server
- 6:41prometheus-adapter
- 7:48Structured Logs: What?
- 8:12Structured Logs: When?
- 12:18Structured Logs: With Context
- 14:59Structured Logs: Who?
- 19:10Traces: Control-Plane
- 22:06Metrics Woes
- 24:49Metrics Stability
- 25:48Metrics Cardinality Enforcement
- 27:04Future Efforts
- 28:10How to contribute
related talks
24mSIG Instrumentation Introduction and Deep Dive
40mSIG Instrumentation Introduction And Deep Dive
28mSIG Instrumentation Introduction and Deep Dive
36mSIG Instrumentation: Intro, Deep Dive and Recent...
37mSIG Instrumentation Intro
26mIntro and Deep Dive: Kubernetes SIG Instrumentation
28mIntro and Deep Dive: Kubernetes SIG Instrumentation
28mKubernetes SIG Instrumentation - Intro