Bird
0
0

You created a ServiceMonitor but Prometheus is not scraping metrics from your service. Which of these is a likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Monitoring and Logging
You created a ServiceMonitor but Prometheus is not scraping metrics from your service. Which of these is a likely cause?
AThe ServiceMonitor selector labels do not match the service labels
BThe Prometheus server is not running on the cluster
CThe service port is not exposed in the ServiceMonitor endpoints
DAll of the above
Step-by-Step Solution
Solution:

  1. Step 1: Check label matching

    If ServiceMonitor selector labels don't match service labels, Prometheus won't find the service.

  2. Step 2: Verify Prometheus server status and endpoint config

    Prometheus must be running and the service port must be correctly specified in endpoints to scrape metrics.

  3. Final Answer:

    All of the above -> Option D

  4. Quick Check:

    Any mismatch or missing config stops scraping [OK]
Quick Trick: Check labels, server status, and endpoints all match [OK]
Common Mistakes:
  • Only checking one cause and ignoring others
  • Assuming Prometheus always runs by default
  • Forgetting to expose correct port in ServiceMonitor

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Advanced Deployment Patterns - Progressive delivery concept - Quiz 11easy Advanced Deployment Patterns - Feature flags in Kubernetes - Quiz 12easy Monitoring and Logging - Container logging architecture - Quiz 5medium Monitoring and Logging - Grafana for visualization - Quiz 1easy Operators and Custom Resources - OperatorHub for community operators - Quiz 11easy Production Best Practices - Priority classes for critical workloads - Quiz 6medium RBAC and Security - Roles and ClusterRoles - Quiz 7medium Service Mesh - Observability with service mesh - Quiz 1easy Service Mesh - Istio overview - Quiz 9hard Troubleshooting - Debugging service connectivity - Quiz 9hard