Prometheus for Docker monitoring - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Prometheus Docker container startup output

You run the following command to start Prometheus in Docker with a custom configuration file. What is the expected output in the Docker logs indicating Prometheus started successfully?

Docker

docker run -d --name prometheus -p 9090:9090 -v /home/user/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus

A level=warn ts=... msg="Deprecated flag used" ...

B Error: failed to load config file: open /etc/prometheus/prometheus.yml: no such file or directory

C level=info ts=... msg="Starting Prometheus" ...

D level=error ts=... msg="Failed to bind to port 9090" ...

💡 Hint

Look for a log message that confirms Prometheus started without errors.

When Prometheus starts successfully, it logs an info level message with 'Starting Prometheus'. Errors about config file or port binding indicate startup failure.

❓ Configuration

intermediate

Prometheus scrape config for Docker containers

Which Prometheus scrape configuration snippet correctly scrapes metrics from Docker containers exposing metrics on port 9100?

A

scrape_configs:
  - job_name: 'docker'
    static_configs:
      - targets: ['localhost:9100']

B

scrape_configs:
  - job_name: 'docker'
    docker_sd_configs:
      - host: 'unix:///var/run/docker.sock'
        port: 9100

C

scrape_configs:
  - job_name: 'docker'
    file_sd_configs:
      - files: ['/etc/prometheus/docker_targets.yml']

D

scrape_configs:
  - job_name: 'docker'
    kubernetes_sd_configs:
      - role: pod

💡 Hint

Docker service discovery uses the Docker socket and port configuration.

Option B uses docker_sd_configs with the Docker socket and port 9100, which is the correct way to discover Docker containers exposing metrics.

❓ Troubleshoot

advanced

Prometheus cannot scrape Docker container metrics

You configured Prometheus to scrape Docker containers on port 9100, but no metrics appear in Prometheus UI. Which is the most likely cause?

A Docker containers do not expose metrics on port 9100

B Prometheus configuration file has invalid YAML syntax

C Prometheus port 9090 is blocked by firewall

D Prometheus container lacks access to Docker socket

💡 Hint

Prometheus needs permission to access Docker socket for service discovery.

Without access to the Docker socket, Prometheus cannot discover containers to scrape metrics from, even if containers expose metrics correctly.

🔀 Workflow

advanced

Steps to monitor Docker containers with Prometheus

What is the correct order of steps to set up Prometheus monitoring for Docker containers exposing metrics on port 9100?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,2,1,4

💡 Hint

Think about starting containers first, then Prometheus, then configuration, then verification.

You must first run containers exposing metrics, then start Prometheus with access to Docker socket, configure scraping, and finally verify in UI.

✅ Best Practice

expert

Best practice for Prometheus Docker monitoring security

Which option is the best practice to securely run Prometheus monitoring Docker containers without exposing the Docker socket to Prometheus container?

A Use a Prometheus exporter sidecar container per Docker container

B Mount the Docker socket read-only into Prometheus container

C Run Prometheus on the host machine with full Docker socket access

D Disable Docker socket access and scrape metrics via container IPs only

💡 Hint

Consider isolation and minimal permissions for security.

Using a sidecar exporter per container avoids giving Prometheus direct access to the Docker socket, improving security by isolating permissions.

Practice

1. What is the main role of Prometheus when monitoring Docker containers?

easy

A. To run Docker containers automatically

B. To collect and store metrics from Docker containers

C. To build Docker images from Dockerfiles

D. To replace Docker Engine for container management

Solution

1. Step 1: Understand Prometheus purpose

   Prometheus is designed to collect and store metrics data from various sources, including Docker containers.

2. Step 2: Differentiate from other Docker tools

   Prometheus does not run containers, build images, or replace Docker Engine; it focuses on monitoring.

3. Final Answer:

   To collect and store metrics from Docker containers -> Option B

4. Quick Check:

   Prometheus = Metrics collection [OK]

Hint: Remember: Prometheus collects data, not runs containers [OK]

Common Mistakes:

• Confusing Prometheus with Docker Engine
• Thinking Prometheus builds images
• Assuming Prometheus runs containers

2. Which Docker command correctly starts cAdvisor to provide metrics for Prometheus?

easy

A. docker run --name cadvisor -p 8080:8080 gcr.io/cadvisor/cadvisor:latest

B. docker run --name cadvisor -p 8080:8080 google/cadvisor:latest

C. docker run --name cadvisor -p 9090:9090 prom/cadvisor:latest

D. docker run --name cadvisor -p 9090:8080 google/cadvisor:stable

Solution

1. Step 1: Identify correct cAdvisor image and port

   The official cAdvisor image is hosted at gcr.io/cadvisor/cadvisor:latest and listens on port 8080.

2. Step 2: Check port mapping and image name

   docker run --name cadvisor -p 8080:8080 gcr.io/cadvisor/cadvisor:latest correctly maps port 8080:8080 and uses the official image name.

3. Final Answer:

   docker run --name cadvisor -p 8080:8080 gcr.io/cadvisor/cadvisor:latest -> Option A

4. Quick Check:

   cAdvisor image and port = docker run --name cadvisor -p 8080:8080 gcr.io/cadvisor/cadvisor:latest [OK]

Hint: Official cAdvisor image is gcr.io/cadvisor/cadvisor:latest [OK]

Common Mistakes:

• Using wrong image repository
• Mapping wrong ports
• Using outdated or incorrect image tags

3. Given this Prometheus scrape config snippet for Docker monitoring:

scrape_configs:
  - job_name: 'cadvisor'
    static_configs:
      - targets: ['localhost:8080']

What will Prometheus do when started with this config?

medium

A. Fail to start due to invalid config syntax

B. Scrape metrics from Docker Engine API on port 8080

C. Scrape metrics from all Docker containers directly

D. Scrape metrics from cAdvisor running on localhost port 8080

Solution

1. Step 1: Analyze scrape_configs job_name and targets

   The job 'cadvisor' targets 'localhost:8080', which is the default cAdvisor port.

2. Step 2: Understand Prometheus scraping behavior

   Prometheus will scrape metrics from the specified target, not Docker Engine API or all containers directly.

3. Final Answer:

   Scrape metrics from cAdvisor running on localhost port 8080 -> Option D

4. Quick Check:

   Prometheus scrapes targets listed = Scrape metrics from cAdvisor running on localhost port 8080 [OK]

Hint: Targets in scrape_configs define where Prometheus scrapes [OK]

Common Mistakes:

• Confusing cAdvisor with Docker Engine API
• Assuming Prometheus scrapes containers directly
• Thinking config syntax is invalid

4. You started Prometheus and cAdvisor with Docker Compose, but Prometheus shows no metrics from cAdvisor. What is the likely cause?

medium

A. Prometheus cannot scrape metrics from port 9090

B. Prometheus config has wrong job_name

C. cAdvisor container is not exposing port 8080 to Prometheus

D. Docker Compose file is missing image tags

Solution

1. Step 1: Check port exposure between cAdvisor and Prometheus

   If cAdvisor does not expose port 8080 or network is misconfigured, Prometheus cannot scrape metrics.

2. Step 2: Verify other options

   Wrong job_name or missing image tags usually cause errors but not silent no metrics; port 9090 is Prometheus default, not cAdvisor.

3. Final Answer:

   cAdvisor container is not exposing port 8080 to Prometheus -> Option C

4. Quick Check:

   Port exposure needed for scraping = cAdvisor container is not exposing port 8080 to Prometheus [OK]

Hint: Check port mapping between containers first [OK]

Common Mistakes:

• Ignoring port exposure issues
• Assuming job_name mismatch causes no metrics
• Confusing Prometheus and cAdvisor ports

5. You want to monitor multiple Docker hosts with Prometheus and cAdvisor. Which setup is best?

hard

A. Run cAdvisor on each host exposing metrics, configure Prometheus to scrape all hosts

B. Run one cAdvisor container on a central host to monitor all hosts

C. Run Prometheus on each host and aggregate metrics manually

D. Use Docker Compose to run a single cAdvisor and Prometheus on one host only

Solution

1. Step 1: Understand cAdvisor scope

   cAdvisor monitors containers on the host it runs on; to monitor multiple hosts, run cAdvisor on each host.

2. Step 2: Configure Prometheus for multi-host scraping

   Prometheus can scrape metrics from multiple cAdvisor instances by listing all hosts in its config.

3. Step 3: Evaluate other options

   Central cAdvisor cannot monitor other hosts; running Prometheus on each host complicates aggregation; single host setup misses other hosts.

4. Final Answer:

   Run cAdvisor on each host exposing metrics, configure Prometheus to scrape all hosts -> Option A

5. Quick Check:

   One cAdvisor per host + Prometheus scrape all = Run cAdvisor on each host exposing metrics, configure Prometheus to scrape all hosts [OK]

Hint: One cAdvisor per host, Prometheus scrapes all [OK]

Common Mistakes:

• Thinking one cAdvisor can monitor all hosts
• Running multiple Prometheus instances unnecessarily
• Ignoring multi-host scraping config