google /cadvisor
Analyzes resource usage and performance characteristics of running containers.
★ 19,530⑂ 2,504👁 361⑃ 2,266● 1,675▤ 126
+1
Daily
+15
Weekly
+50
Monthly
19,530
stars
2,504
forks
361
watchers
2,266
prs
1,675
issues
126
releases
README
!cAdvisor !test status cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running containers. It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide. cAdvisor has native support for Docker containers and should support just about any other container type out of the box. We strive for support across the board so feel free to open an issue if that is not the case. cAdvisor's container abstraction is based on lmctfy's so containers are inherently nested hierarchically. Quick Start: Running cAdvisor in a Docker Container To quickly tryout cAdvisor on your machine with Docker, we have a Docker image that includes everything you need to get started. You can run a single cAdvisor to monitor the whole machine. Simply run: VERSION=0.55.1 use the latest release version from https://github.com/google/cadvisor/releases sudo docker run \ --volume=/:/rootfs:ro \ --volume=/var/run:/var/run:ro \ --volume=/sys:/sys:ro \ --volume=/var/lib/docker/:/var/lib/docker:ro \ --volume=/dev/disk/:/dev/disk:ro \ --publish=8080:8080 \ --detach=true \ --name=cadvisor \ --privileged \ --device=/dev/kmsg \ ghcr.io/google/cadvisor:$VERSION for versions prior to v0.53.0, use gcr.io/cadvisor/cadvisor instead cAdvisor is now running (in the background) on http://localhost:8080. The setup includes directories with Docker state cAdvisor needs to observe. Note: If you're running on CentOS, Fedora, or RHEL (or are using LXC), take a look at our running instructions. We have detailed instructions on running cAdvisor standalone outside of Docker. cAdvisor running options may also be interesting for advanced usecases. If you want to build your own cAdvisor Docker image, see our deployment page. For Kubernetes users, cAdvisor can be run as a daemonset. See the instructions for how to get started, and for how to kustomize it to fit your needs. Building and Testing See the more detailed instructions in the build page. This includes instructions for building and deploying the cAdvisor Docker image. Exporting stats cAdvisor supports exporting stats to various storage plugins. See the documentation for more details and examples. Web UI cAdvisor exposes a web UI at its port: http://:/ See the documentation for more details. Remote REST API & Clients cAdvisor exposes its raw and processed stats via a versioned remote REST API. See the API's documentation for more information. There is also an official Go client implementation in the client directory. See the documentation for more information. Roadmap cAdvisor aims to improve the resource usage and performance characteristics of running
Top issues
#3772Registration of the docker container factory failed after update to v0.54.125 comments · 2025-12-07#3777Support pod/container level ```container_fs_usage_bytes```8 comments · 2025-12-10#3703Multi Arch Build for linux/arm/v7 is missing8 comments · 2025-06-17#3831Add support for InfluxDB 2 and InfluxDB 3 Core5 comments · 2026-01-29#3737`container_spec_cpu_shares` will use wrong cgroups v2 conversion formula for runc v1.3.2+4 comments · 2025-10-03#3728Error when starting cadvisor to monitor rootless docker containers (permission denied on other users' /sys/fs/cgroup/user.slice)4 comments · 2025-09-15#3710Missing s390x Artifacts in v0.53.04 comments · 2025-07-09#3958AppMetrics are not being collected due to incorrect / incomplete deprecation of ApplicationMetricsCountLimit3 comments · 2026-10-28
Latest release
cAdvisor v0.60.6 v0.60.6 2026-09-18What's Changed workflows: mirror release tags to lib/ module tags by @dims in https://github.com/google/cadvisor/pull/3914 fs/zfs: fall back to VFS when zfs stats are unavailable by @locker95 in https://github.com/google/cadvisor/pull/3918 storage/stdout: nil-check Cpu, Network, and Memory stats by @locker95 in https://github.com/google/cadvisor/pull/3917 Treat memory-only NUMA nodes as valid topology by @joejulian in https://github.com/google/cadvisor/pull/3931 New Contributors @locker95 made their first contribution in https://github.com/google/cadvisor/pull/3918 @joejulian m