Skip to content

docs(monitoring): record cAdvisor #3860 status and disk-metrics fallback #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PBernaerts merged 1 commit into from
Jul 11, 2026
Merged

docs(monitoring): record cAdvisor #3860 status and disk-metrics fallback #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions monitoring/scripts/docker-stats-textfile.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,11 @@
# cAdvisor can't collect metrics on this host (Docker 29 + overlayfs snapshotter,
# google/cadvisor#3860), so we sample the Docker stats API instead — it reads cgroup-v2
# usage directly and is independent of the storage-driver layer-resolution bug.
# Status 2026-07-11: #3860 still open at cAdvisor v0.60.5. Only disk-stats collection is
# broken; `--disable_metrics=disk` makes cAdvisor work (per-container CPU/mem/net, no
# container_fs_*). Deliberately staying with this script: no privileged container, no 15s
# sampling loop, and it exposes the anon-memory metric dashboards/alerts depend on.
# Upstream fix to watch: google/cadvisor#3892 (+ #3910).
#
# Metrics {name=...}:
# docker_container_cpu_percent CPU% across all cores
Expand Down