Demystifying Monitoring and Debugging on Windows Containers
Talkat Observability Day 2025 · on Tuesday, 2025-04-01· at 15:55· Level 1 | Hall Entrance S10 | Room C·
summary
Demo deploys a Prometheus stack that uses Windows exporter on port 9182 with default CPU/memory/OS collectors plus optional container/process/net collectors, a ServiceMonitor, and Grafana dashboards; nodes run Containerd on Windows Server 2022. Debugging uses HostProcess container base image (~6–8KB) launched via a custom kubectl debug yaml to get host file access, run collect-logs.ps1 to capture HNS ETL traces, and kubectl cp to retrieve logs for offline analysis. Metrics and node-level debugging both work end-to-end.
AI-written summary · about
chapters (11)
- 0:00Windows container monitoring intro
- 1:04Why Windows containers matter
- 2:50Kubernetes Windows nodes setup
- 4:13Monitoring gaps in Windows
- 4:33Host process containers explained
- 5:38Monitoring Windows nodes
- 7:45Debugging Windows nodes
- 9:29Host process containers for debug
- 13:49Demo and Grafana dashboard
- 17:21Live Windows node debug
- 22:14Summary and resources
related talks
36mMastering Windows Monitoring in Kubernetes Environments
36mMastering Windows Monitoring in Kubernetes Environments
34mDebugging at Scale in Production - Deep into Your Containers with Kubectl Debug
24mPractical Kubernetes Monitoring with Prometheus
32mDemocratizing Application Monitoring with Prometheus
37mKubernetes, Monitoring with Prometheus and Grafana
46mLeveraging Prometheus Service Monitor and Pod Monitor for Enhanced Kubernetes Monitoring
25mDebugging at Scale in Production with kubectl debug
