Prometheus and Grafana integration in Kafka - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Prometheus scrape configuration output

Given this Prometheus scrape config snippet, what will be the value of the 'job' label for metrics scraped from Kafka exporters?

Kafka

scrape_configs:
  - job_name: 'kafka'
    static_configs:
      - targets: ['localhost:9308']

A kafka

B localhost

C exporter

D 9308

💡 Hint

Look at the job_name field in the scrape_configs section.

The 'job' label in Prometheus metrics is set from the 'job_name' field in the scrape_configs. Here, it is 'kafka'.

🔀 Workflow

intermediate

Steps to visualize Kafka metrics in Grafana

Which sequence correctly describes the steps to visualize Kafka metrics in Grafana after Prometheus is scraping Kafka exporter metrics?

A 1,4,2,3

B 4,1,2,3

C 1,2,4,3

D 4,2,1,3

💡 Hint

Start by ensuring Prometheus is scraping metrics before adding Grafana data source.

First verify Prometheus scrapes metrics (4), then add Prometheus as Grafana data source (1), create dashboard (2), then add panels (3).

❓ Troubleshoot

advanced

Prometheus not scraping Kafka exporter metrics

Prometheus is not collecting metrics from Kafka exporter at localhost:9308. Which configuration mistake causes this?

Kafka

scrape_configs:
  - job_name: 'kafka'
    static_configs:
      - targets: ['localhost:9307']

A Target port is incorrect; should be 9308 not 9307.

B Job name must be 'kafka_exporter' instead of 'kafka'.

C Static configs must use IP address, not 'localhost'.

D Missing scheme: 'http://' before target address.

💡 Hint

Check the port number in the targets list.

The Kafka exporter runs on port 9308 by default. Using 9307 causes Prometheus to fail scraping.

🧠 Conceptual

advanced

Grafana alerting on Kafka lag

Which Prometheus query expression correctly triggers an alert when Kafka consumer lag exceeds 1000 messages?

A avg(kafka_consumergroup_lag) > 1000

B max(kafka_consumergroup_lag) < 1000

C sum(kafka_consumergroup_lag) by (group) > 1000

D kafka_consumergroup_lag > 1000

💡 Hint

Consider grouping lag by consumer group to alert per group.

Summing lag by group and checking if it exceeds 1000 triggers alert for groups with high lag.

✅ Best Practice

expert

Optimizing Prometheus scrape intervals for Kafka exporters

What is the best practice for setting Prometheus scrape interval for Kafka exporters to balance data freshness and system load?

A Set scrape_interval to 5m to reduce load on Kafka exporters.

B Set scrape_interval to 1s for maximum data freshness.

C Set scrape_interval to 1h to minimize Prometheus storage usage.

D Set scrape_interval to 15s to get near real-time metrics without high load.

💡 Hint

Consider typical Kafka metric update frequency and system resource usage.

A 15-second interval balances timely metrics and reasonable load on exporters and Prometheus.