~/talk

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· [observability]
links:none on file
links:none on file
slides:none on file

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

  1. 0:00Windows container monitoring intro
  2. 1:04Why Windows containers matter
  3. 2:50Kubernetes Windows nodes setup
  4. 4:13Monitoring gaps in Windows
  5. 4:33Host process containers explained
  6. 5:38Monitoring Windows nodes
  7. 7:45Debugging Windows nodes
  8. 9:29Host process containers for debug
  9. 13:49Demo and Grafana dashboard
  10. 17:21Live Windows node debug
  11. 22:14Summary and resources
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.