[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4828":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},4828,"cadvisor","google\u002Fcadvisor","google","Analyzes resource usage and performance characteristics of running containers.","",null,"Go",19190,2476,360,43,0,5,14,70,18,45,"Other",false,"master",[],"2026-06-12 02:01:04","![cAdvisor](logo.png \"cAdvisor\")\n\n![test status](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcadvisor\u002Fworkflows\u002FTest\u002Fbadge.svg)\n\ncAdvisor (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.\n\ncAdvisor has native support for [Docker](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker) 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](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Flmctfy)'s so containers are inherently nested hierarchically.\n\n#### Quick Start: Running cAdvisor in a Docker Container\n\nTo 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:\n\n```\nVERSION=0.55.1 # use the latest release version from https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcadvisor\u002Freleases\nsudo docker run \\\n  --volume=\u002F:\u002Frootfs:ro \\\n  --volume=\u002Fvar\u002Frun:\u002Fvar\u002Frun:ro \\\n  --volume=\u002Fsys:\u002Fsys:ro \\\n  --volume=\u002Fvar\u002Flib\u002Fdocker\u002F:\u002Fvar\u002Flib\u002Fdocker:ro \\\n  --volume=\u002Fdev\u002Fdisk\u002F:\u002Fdev\u002Fdisk:ro \\\n  --publish=8080:8080 \\\n  --detach=true \\\n  --name=cadvisor \\\n  --privileged \\\n  --device=\u002Fdev\u002Fkmsg \\\n  ghcr.io\u002Fgoogle\u002Fcadvisor:$VERSION # for versions prior to v0.53.0, use gcr.io\u002Fcadvisor\u002Fcadvisor instead\n```\n\ncAdvisor is now running (in the background) on `http:\u002F\u002Flocalhost:8080`. The setup includes directories with Docker state cAdvisor needs to observe.\n\n**Note**: If you're running on CentOS, Fedora, or RHEL (or are using LXC), take a look at our [running instructions](docs\u002Frunning.md).\n\nWe have detailed [instructions](docs\u002Frunning.md#standalone) on running cAdvisor standalone outside of Docker. cAdvisor [running options](docs\u002Fruntime_options.md) may also be interesting for advanced usecases. If you want to build your own cAdvisor Docker image, see our [deployment](docs\u002Fdeploy.md) page.\n\nFor [Kubernetes](https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes) users, cAdvisor can be run as a daemonset. See the [instructions](deploy\u002Fkubernetes) for how to get started, and for how to [kustomize](https:\u002F\u002Fgithub.com\u002Fkubernetes-sigs\u002Fkustomize#kustomize) it to fit your needs.\n\n## Building and Testing\n\nSee the more detailed instructions in the [build page](docs\u002Fdevelopment\u002Fbuild.md). This includes instructions for building and deploying the cAdvisor Docker image.\n\n## Exporting stats\n\ncAdvisor supports exporting stats to various storage plugins. See the [documentation](docs\u002Fstorage\u002FREADME.md) for more details and examples.\n\n## Web UI\n\ncAdvisor exposes a web UI at its port:\n\n`http:\u002F\u002F\u003Chostname>:\u003Cport>\u002F`\n\nSee the [documentation](docs\u002Fweb.md) for more details.\n\n## Remote REST API & Clients\n\ncAdvisor exposes its raw and processed stats via a versioned remote REST API. See the API's [documentation](docs\u002Fapi.md) for more information.\n\nThere is also an official Go client implementation in the [client](client\u002F) directory. See the [documentation](docs\u002Fclients.md) for more information.\n\n## Roadmap\n\ncAdvisor aims to improve the resource usage and performance characteristics of running containers. Today, we gather and expose this information to users. In our roadmap:\n\n- Advise on the performance of a container (e.g.: when it is being negatively affected by another, when it is not receiving the resources it requires, etc).\n- Auto-tune the performance of the container based on previous advise.\n- Provide usage prediction to cluster schedulers and orchestration layers.\n\n## Community\n\nContributions, questions, and comments are all welcomed and encouraged! cAdvisor developers hang out on [Slack](https:\u002F\u002Fkubernetes.slack.com) in the #sig-node channel (get an invitation [here](http:\u002F\u002Fslack.kubernetes.io\u002F)). We also have [discuss.kubernetes.io](https:\u002F\u002Fdiscuss.kubernetes.io\u002F).\n\nPlease reach out and get involved in the project, we're actively looking for more contributors to bring on board!\n\n### Core Team\n* [@bobbypage, Google](https:\u002F\u002Fgithub.com\u002Fbobbypage)\n* [@iwankgb, Independent](https:\u002F\u002Fgithub.com\u002Fiwankgb)\n* [@creatone, Independent](https:\u002F\u002Fgithub.com\u002Fcreatone)\n* [@dims, VMWare](https:\u002F\u002Fgithub.com\u002Fdims)\n* [@mrunalp, RedHat](https:\u002F\u002Fgithub.com\u002Fmrunalp)\n\n### Frequent Collaborators\n* [@haircommander, RedHat](https:\u002F\u002Fgithub.com\u002Fhaircommander)\n\n### Emeritus\n* [@dashpole, Google](https:\u002F\u002Fgithub.com\u002Fdashpole)\n* [@dchen1107, Google](https:\u002F\u002Fgithub.com\u002Fdchen1107)\n* [@derekwaynecarr, RedHat](https:\u002F\u002Fgithub.com\u002Fderekwaynecarr)\n","cAdvisor 是一个用于分析运行中容器资源使用情况和性能特性的工具。它作为一个守护进程运行，收集、聚合、处理并导出关于运行容器的信息，包括资源隔离参数、历史资源使用情况、完整的历史资源使用直方图及网络统计信息。该项目采用 Go 语言编写，具备对 Docker 容器的原生支持，并且理论上可以兼容其他类型的容器。cAdvisor 适合于需要深入了解容器资源消耗细节的场景，如微服务架构下的性能监控与优化、云原生环境中的资源管理等。通过简单的 Docker 命令即可快速部署 cAdvisor 来监控整个机器的状态，同时也提供了作为 Kubernetes DaemonSet 运行的能力，以满足更复杂环境的需求。",2,"2026-06-11 03:00:43","top_language"]