Bird
0
0

You configured Prometheus to scrape cAdvisor but get a connection refused error. What is the most likely fix?

medium📝 Troubleshoot Q6 of 15
Docker - Logging and Monitoring
You configured Prometheus to scrape cAdvisor but get a connection refused error. What is the most likely fix?
ARestart Docker daemon
BIncrease Prometheus memory limits
CCheck if cAdvisor container is running and port 8080 is exposed
DChange Prometheus scrape interval to 1 minute
Step-by-Step Solution
Solution:

  1. Step 1: Diagnose connection refused

    This error means Prometheus cannot reach cAdvisor on the expected port.

  2. Step 2: Verify cAdvisor status and port exposure

    Ensure cAdvisor container is running and port 8080 is mapped to host.

  3. Final Answer:

    Check if cAdvisor container is running and port 8080 is exposed -> Option C

  4. Quick Check:

    Connection refused = cAdvisor down or port closed [OK]
Quick Trick: Verify cAdvisor container and port before checking Prometheus [OK]
Common Mistakes:
  • Restarting Docker daemon unnecessarily
  • Changing scrape interval instead of fixing connection

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - User namespace remapping - Quiz 3easy Docker Security - Read-only filesystem containers - Quiz 10hard Docker Swarm - Service scaling - Quiz 12easy Docker Swarm - Why orchestration matters - Quiz 11easy Docker Swarm - Swarm vs Kubernetes decision - Quiz 8hard Docker in CI/CD - Deploying from CI/CD pipeline - Quiz 15hard Docker in CI/CD - GitLab CI with Docker - Quiz 1easy Image Optimization - Reducing image size strategies - Quiz 8hard Logging and Monitoring - Docker logging drivers - Quiz 10hard Production Patterns - Backup and restore strategies - Quiz 14medium