← Directory

CAdvisor

cAdvisor (Container Advisor) is a background service that collects, aggregates, and exports resource usage and performance metrics for running containers,…

  • Infrastructure
  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
cAdvisor (Container Advisor) is a background service that collects, aggregates, and exports resource usage and performance metrics for running containers, helping container users monitor processor, memory, network, and filesystem activity.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

18/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
553 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

No GitHub repository data collected yet.

Checked 17 days ago - source: GitHub (BigBearTechWorld/cadvisor)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Send metrics to Statsd if you use it If you want cAdvisor to push metrics to Statsd, start it with the flags --storage_driver=statsd and --storage_driver_host=your-host:8125, where 8125 is the usual Statsd port. Without these settings, cAdvisor won't send to your Statsd server and your graphs will stay empty. source
  • Apply the Kubernetes cAdvisor Daemonset If you are installing on Kubernetes, apply the example Daemonset (a Kubernetes recipe that starts one cAdvisor container on each node) by running kubectl kustomize deploy/kubernetes/overlays/examples | kubectl apply -f -. If you skip it, cAdvisor is not created and your cluster has no container resource metrics. source
  • Use a perf events file for CPU counters If you want detailed CPU counters called perf events, create the JSON config file with the core and uncore event names you need. Without that file, those advanced perf metrics will not be set up or shown. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What do I need to run cAdvisor with Docker Compose?

Add one container that has access to the host's container runtime data.

How do I configure cAdvisor to push metrics to Statsd?

Start cAdvisor with the flags --storage_driver=statsd and --storage_driver_host=your-host:8125. Without these settings, cAdvisor will not send metrics to your Statsd server and your graphs will stay empty.

How do I enable detailed perf events CPU counters?

Create a JSON config file with the core and uncore event names you need. Without that file, those advanced perf metrics will not be set up or shown.

Why isn't cAdvisor appearing as a Prometheus target?

Check the Prometheus container logs first. The container may not resolve cAdvisor or node_exporter, or the scrape config may have the wrong ports for the targets.

Answers sourced from github.com, github.com, www.dash0.com, www.reddit.com

Community

Collected 11 days ago - public community threads