Bird
Raised Fist0

You configured Prometheus to scrape Kafka metrics but Grafana shows no data. Which is the most likely cause?

medium📝 Troubleshoot Q14 of Q15
Kafka - Monitoring and Operations
You configured Prometheus to scrape Kafka metrics but Grafana shows no data. Which is the most likely cause?
APrometheus scrape interval is too short
BGrafana dashboard is not connected to Prometheus
CKafka metrics endpoint is not exposed or unreachable
DKafka broker is down
Step-by-Step Solution
Solution:

  1. Step 1: Check Prometheus scraping setup

    If Kafka metrics endpoint is not exposed or unreachable, Prometheus cannot collect data.

  2. Step 2: Understand impact on Grafana

    Without data in Prometheus, Grafana dashboards show no metrics.

  3. Final Answer:

    Kafka metrics endpoint is not exposed or unreachable -> Option C

  4. Quick Check:

    No data means no scrape target reachable [OK]
Quick Trick: No data? Check if metrics endpoint is reachable first [OK]
Common Mistakes:
MISTAKES
  • Blaming Grafana connection before checking Prometheus data
  • Assuming Kafka broker down always causes no data
  • Thinking scrape interval too short causes no data

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Kafka Connect - Source connectors - Quiz 12easy Kafka Streams - Windowed operations - Quiz 7medium Kafka Streams - Why stream processing transforms data - Quiz 1easy Kafka with Java/Python - Python consumer - Quiz 11easy Kafka with Java/Python - Client metrics monitoring - Quiz 8hard Message Delivery Semantics - Consumer offset commit strategies - Quiz 11easy Monitoring and Operations - Why monitoring prevents outages - Quiz 7medium Monitoring and Operations - Consumer lag monitoring - Quiz 10hard Schema Registry - Why schema management prevents data issues - Quiz 5medium Schema Registry - Schema validation in producers - Quiz 3easy