After deploying a ServiceMonitor, Prometheus is not scraping your application's metrics. Which of the following is the most probable reason?

medium📝 Troubleshoot Q6 of 15

Kubernetes - Monitoring and Logging

AThe application is exposing metrics on a non-standard port that Prometheus cannot detect

BPrometheus does not support scraping metrics from Kubernetes services

CThe ServiceMonitor's label selector does not match the labels on the target service

DThe ServiceMonitor resource is missing the 'apiVersion' field

Step-by-Step Solution

Solution:

Step 1: Check ServiceMonitor configuration
ServiceMonitor uses label selectors to identify which services to scrape.
Step 2: Identify mismatch issue
If the selector labels do not match the service labels, Prometheus will not scrape metrics.
Step 3: Evaluate other options
Prometheus does not support scraping metrics from Kubernetes services is incorrect because Prometheus supports scraping Kubernetes services. The application is exposing metrics on a non-standard port that Prometheus cannot detect is less likely if the port is correctly specified in ServiceMonitor. The ServiceMonitor resource is missing the 'apiVersion' field would cause resource creation failure.
Final Answer:
The ServiceMonitor's label selector does not match the labels on the target service -> Option C
Quick Check:
Label selectors must match service labels for scraping [OK]

Quick Trick: Label selectors must match target service labels [OK]

Common Mistakes:

Master "Monitoring and Logging" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes