Monitoring Containers with cAdvisor — Part 2 of My Previous Blog Series
Raees Qazi | DevOps Engineer | Learner | Mentor | Creator | CEO-Briller Technologies Today I’m going to talk about cAdvisor , which continues from my previous blog: https://brillertechnologies.blogspot.com/2025/11/prometheus-and-grafana-projectpart-1-by.html After running our application, the next important step is monitoring — and for that, we use cAdvisor , a monitoring tool created by Google. What is cAdvisor? cAdvisor stands for Container Advisor . Its job is to show the resource usage and performance statistics of your running containers — things like CPU, RAM, network, and filesystem usage. cAdvisor reads data directly from Docker’s internal directory, which is located at: /var/lib/docker So it needs read access to this path. Configuring cAdvisor in Docker Compose Now let’s update our docker-compose.yml file to include cAdvisor. Open the file: vim docker-compose. yml Networks Section networks: monitoring: driver: bridge Services Section 1. No...