Automating Prometheus Setup for Efficient Docker Monitoring

Ashish Dwivedi
5 min readJul 24, 2023



In our previous article, we explored the manual setup of Prometheus, cAdvisor, and Node Exporter for monitoring Docker containers and host systems. However, as our monitoring environment grows, automating the setup becomes crucial for efficiency and scalability. In this article, we will introduce a Bash script that automates the installation and configuration of Prometheus, cAdvisor, and Node Exporter on an Ubuntu machine. Additionally, we’ll discuss essential metrics to monitor, helping you fine-tune your Dockerized applications for optimal performance and reliability.

Automating the Setup with a Bash Script

To automate the installation and configuration of Prometheus, cAdvisor, and Node Exporter, we’ll use a bash script. This script will perform the following tasks:

  1. Install Docker and Docker Compose
  2. Download and configure Node Exporter for host metrics
  3. Set up cAdvisor for container metrics
  4. Configure Prometheus to scrape metrics from Node Exporter and cAdvisor

# Install Docker
sudo apt-get update
sudo apt-get install -y

# Install Docker Compose
sudo curl -L "$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

# Download and configure Node Exporter
VERSION="0.18.1" # Replace with the latest version
wget "${VERSION}/node_exporter-${VERSION}.linux-amd64.tar.gz"
tar xvfz "node_exporter-${VERSION}.linux-amd64.tar.gz"
sudo mv "node_exporter-${VERSION}.linux-amd64/node_exporter" /usr/local/bin/
sudo useradd -rs /bin/false node_exporter

# Create systemd service for Node Exporter
sudo tee /etc/systemd/system/node_exporter.service > /dev/null <<EOT
Description=Node Exporter



# Start and enable Node Exporter service
sudo systemctl daemon-reload
sudo systemctl enable node_exporter
sudo systemctl start node_exporter

# Set up cAdvisor
sudo tee /path/to/docker-compose.yml > /dev/null <<EOT
version: '3.7'
image: google/cadvisor:latest
container_name: cadvisor
restart: always
- "8080:8080"
- /:/rootfs:ro
- /var/run:/var/run:rw
- /sys:/sys:ro
- /var/lib/docker/:/var/lib/docker:ro

# Start cAdvisor container
sudo docker-compose -f /path/to/docker-compose.yml up -d

# Configure Prometheus to scrape metrics
sudo tee /path/to/prometheus.yml > /dev/null <<EOT
scrape_interval: 15s

- job_name: 'prometheus'
scrape_interval: 5s
- targets: ['localhost:9090']

- job_name: 'node_exporter'
scrape_interval: 5s
- targets: ['localhost:9100']

- job_name: 'cadvisor'
scrape_interval: 5s
- targets: ['localhost:8080']
# Restart Prometheus to apply changes
sudo systemctl restart prometheus

Essential Metrics to Keep Your Docker Environment Healthy

If you’re using Docker to manage your applications, it’s crucial to keep a close eye on various metrics to ensure that everything is running smoothly. Monitoring these metrics helps you identify potential issues and make adjustments to optimize your system’s performance. we’ll explore some essential metrics you should be monitoring for both the host system and Docker containers in simple and easy-to-understand terms.

Host Metrics:

1. Host CPU Usage: The CPU (Central Processing Unit) acts as the brain of your computer, responsible for executing tasks and calculations. Similarly, in a Docker environment, the host’s CPU plays a crucial role in managing various processes, including Docker containers. Monitoring the host CPU usage is essential because it allows you to keep track of how much of the CPU’s power is being utilized by Docker and other running processes. This information helps you ensure that there is enough CPU capacity available to efficiently handle all your containers and applications.

2. Host Memory Usage: Just like our computers need memory (RAM) to run applications smoothly, Docker containers also require memory to function properly. Monitoring the host’s memory usage allows you to keep a close eye on how much memory Docker and other applications are using. This is important because it helps you identify any memory-related issues that might arise, such as when a container uses up an excessive amount of memory or when there’s a memory leak, causing the system to become slow or unstable.

3. Host Disk Space: Think of disk space as the storage capacity of your computer. In a Docker environment, it’s essential to keep track of how much disk space Docker is utilizing. Monitoring the host disk space ensures that Docker has enough room to store all the necessary data, such as container images, logs, and application files. Running out of disk space can lead to storage problems and potentially cause disruptions in your Docker environment.

Docker Container Metrics:

4. Container CPU Usage: Each Docker container acts like a mini-brain with its own CPU, responsible for processing tasks specific to that container. Monitoring the CPU usage of individual containers is crucial because it allows you to understand how much CPU power each container is utilizing. By doing so, you can optimize the allocation of CPU resources among different containers, ensuring that high-priority containers get the necessary computing power and that the overall system runs more efficiently.

5. Throttled CPU Time: Sometimes, a container might attempt to use more CPU power than it’s allowed to use, and the system might “throttle” it, meaning it limits the container’s CPU access to prevent it from consuming an excessive amount of resources. Monitoring the throttled CPU time helps you identify if any containers are being held back and not getting the CPU resources they need. By understanding this metric, you can adjust the CPU share constraints for specific containers, ensuring that they get the resources they require.

6. Container Memory Fail Counters: Containers have specific memory requirements, and they are allocated a certain amount of memory to function correctly. Monitoring memory fail counters allows you to keep an eye on containers that might be requesting more memory than they are allowed to have. By doing so, you can plan your resource allocation better and prevent memory-related issues, such as containers crashing or slowing down due to insufficient memory.

7. Container Memory Usage: Similar to monitoring host memory usage, keeping track of how much memory each container is using is essential. This helps you set appropriate memory limits for containers, ensuring they don’t use too much or too little memory. Properly managing memory usage is crucial for maintaining optimal performance and avoiding memory-related problems.

8. Container Swap: Swap acts as a backup memory when the actual RAM is full. Monitoring container swap usage helps you detect containers that might be using an excessive amount of swap space. Relying too much on swap instead of RAM can lead to performance issues and slow down your system.

9. Container Disk I/O: Disk I/O refers to how quickly data is read from or written to the disk. Monitoring this metric for containers helps you identify any bottlenecks in their disk usage. Slow disk I/O can impact the performance of your applications, and addressing such issues can lead to better overall system performance.

10. Container Network Metrics: Monitoring network metrics helps you understand how much data is being sent and received by containers. Unexpected spikes in network usage could indicate potential issues like a Denial of Service (DoS) attack or other network-related problems. Keeping an eye on network metrics helps you ensure the security and reliability of your Docker environment.


Automating the setup of Prometheus, cAdvisor, and Node Exporter can save time and streamline the monitoring process. By utilizing the bash script provided in this article, you can effortlessly configure your monitoring environment. Monitor essential metrics for your host system and Docker containers to ensure optimal performance and reliability. Fine-tune your application based on performance testing results, and remember that monitoring and fine-tuning are continuous processes for a robust Docker environment.

Happy monitoring………………