Key broker metrics in Kafka - Mini Project: Build & Apply

Key broker metrics

📖 Scenario: You are working with a Kafka cluster and want to monitor key broker metrics to ensure the system is running smoothly.

🎯 Goal: Build a simple program that collects and displays key Kafka broker metrics such as bytes in/out per second and request rates.

📋 What You'll Learn

Create a dictionary with exact metric names and initial values

Add a configuration variable for the minimum threshold to alert

Use a loop to filter metrics above the threshold

Print the filtered metrics

💡 Why This Matters

🌍 Real World

Monitoring Kafka broker metrics helps keep the system healthy and detect issues early.

💼 Career

Understanding how to filter and display key metrics is useful for roles in DevOps, site reliability engineering, and backend development.

1

Create initial metrics dictionary

Create a dictionary called broker_metrics with these exact entries: 'BytesInPerSec': 1200, 'BytesOutPerSec': 1500, 'RequestRate': 300, 'FailedRequests': 5

Kafka

# Create the dictionary 'broker_metrics' with the specified entries
# Your code here

Hint

Use curly braces to create a dictionary with the exact keys and values.

2

Add threshold configuration

Create a variable called threshold and set it to 1000 to filter important metrics

Kafka

broker_metrics = {'BytesInPerSec': 1200, 'BytesOutPerSec': 1500, 'RequestRate': 300, 'FailedRequests': 5}
# Create the variable 'threshold' and set it to 1000
# Your code here

Hint

Just assign the number 1000 to the variable threshold.

3

Filter metrics above threshold

Create a new dictionary called important_metrics using a dictionary comprehension that includes only items from broker_metrics where the value is greater than threshold

Kafka

broker_metrics = {'BytesInPerSec': 1200, 'BytesOutPerSec': 1500, 'RequestRate': 300, 'FailedRequests': 5}
threshold = 1000
# Create 'important_metrics' with items from 'broker_metrics' where value > threshold
# Your code here

Hint

Use a dictionary comprehension with for key, value in broker_metrics.items() and an if condition.

4

Print the filtered metrics

Write a print statement to display the important_metrics dictionary

Kafka

broker_metrics = {'BytesInPerSec': 1200, 'BytesOutPerSec': 1500, 'RequestRate': 300, 'FailedRequests': 5}
threshold = 1000
important_metrics = {key: value for key, value in broker_metrics.items() if value > threshold}
# Print the 'important_metrics' dictionary
# Your code here

Hint

Use print(important_metrics) to show the filtered dictionary.

Practice

1.

What does the MessagesInPerSec metric in Kafka broker monitoring indicate?

easy

A. The number of messages the broker receives per second

B. The number of active connections to the broker

C. The total disk space used by the broker

D. The number of partitions in the broker

Solution

1. Step 1: Understand the metric name

   The metric MessagesInPerSec literally means messages coming in per second to the broker.

2. Step 2: Match the metric to its meaning

   This metric counts how many messages the broker receives every second, showing its input load.

3. Final Answer:

   The number of messages the broker receives per second -> Option A

4. Quick Check:

   MessagesInPerSec = messages received per second [OK]

Hint: Look for 'In' to find incoming message rate [OK]

Common Mistakes:

• Confusing message count with connection count
• Thinking it measures disk usage
• Mixing it up with partition count

2.

Which of the following is the correct JMX metric name to monitor the broker's outgoing bytes per second?

easy

A. MessagesOutPerSec

B. BytesInPerSec

C. BytesOutPerSec

D. BytesTotalPerSec

Solution

1. Step 1: Identify the direction of data flow

   Outgoing bytes means data sent out from the broker, so the metric should say 'Out'.

2. Step 2: Match the exact metric name

   The correct metric for outgoing bytes per second is BytesOutPerSec.

3. Final Answer:

   BytesOutPerSec -> Option C

4. Quick Check:

   Outgoing bytes = BytesOutPerSec [OK]

Hint: Look for 'Out' and 'Bytes' in metric name [OK]

Common Mistakes:

• Choosing BytesInPerSec which is incoming data
• Confusing messages with bytes
• Using a non-existent metric name

3.

Given the following JMX metric values for a Kafka broker:
MessagesInPerSec = 500
BytesInPerSec = 1024000
BytesOutPerSec = 2048000
What does this tell you about the broker's activity?

medium

A. The broker's incoming and outgoing bytes are equal

B. The broker is receiving more messages than it sends out

C. The broker is idle with no message traffic

D. The broker is sending out twice as much data as it receives in messages

Solution

1. Step 1: Analyze the metric values

   MessagesInPerSec is 500, BytesInPerSec is 1,024,000 bytes, BytesOutPerSec is 2,048,000 bytes.

2. Step 2: Compare incoming and outgoing bytes

   Outgoing bytes (2,048,000) is exactly twice the incoming bytes (1,024,000), meaning the broker sends out twice as much data as it receives.

3. Final Answer:

   The broker is sending out twice as much data as it receives in messages -> Option D

4. Quick Check:

   BytesOutPerSec = 2 x BytesInPerSec [OK]

Hint: Compare BytesOutPerSec and BytesInPerSec values [OK]

Common Mistakes:

• Ignoring the difference between bytes and messages
• Assuming equal incoming and outgoing bytes
• Misreading the numeric values

4.

Consider this snippet monitoring Kafka broker metrics in Java:

double bytesIn = jmxClient.getAttribute("kafka.server:type=BrokerTopicMetrics,name=BytesInPerSec");
double bytesOut = jmxClient.getAttribute("kafka.server:type=BrokerTopicMetrics,name=BytesOutPerSec");
if (bytesIn > bytesOut) {
    System.out.println("More incoming data");
} else {
    System.out.println("More outgoing data");
}

What is the likely bug in this code?

medium

A. The code does not handle the case when bytesIn equals bytesOut

B. The comparison should use >= to handle equal values

C. The metric names are incorrect and will cause an error

D. The JMX attribute values should be cast to int, not double

Solution

1. Step 1: Review the if-else logic

   The code checks if bytesIn is greater than bytesOut, else prints "More outgoing data".

2. Step 2: Identify missing case handling

   If bytesIn equals bytesOut, the else block runs, printing "More outgoing data" which is misleading.

3. Final Answer:

   The code does not handle the case when bytesIn equals bytesOut -> Option A

4. Quick Check:

   Equal values need explicit handling [OK]

Hint: Check if equal values are handled in if-else [OK]

Common Mistakes:

• Assuming metric names are wrong
• Ignoring equal value scenario
• Casting to wrong data type without error

5.

You want to alert if the Kafka broker's RequestHandlerAvgIdlePercent metric drops below 20%, indicating high load. Which approach correctly implements this check in pseudocode?

1. Fetch RequestHandlerAvgIdlePercent metric value
2. If value < 20 then alert 'High broker load'

hard

A. if (RequestHandlerAvgIdlePercent > 20) { alert('High broker load'); }

B. if (RequestHandlerAvgIdlePercent < 20) { alert('High broker load'); }

C. if (RequestHandlerAvgIdlePercent == 20) { alert('High broker load'); }

D. if (RequestHandlerAvgIdlePercent != 20) { alert('High broker load'); }

Solution

1. Step 1: Understand the metric meaning

   RequestHandlerAvgIdlePercent shows how idle the request handler threads are; lower means busier.

2. Step 2: Apply the alert condition

   If this value is less than 20%, it means the broker is busy, so alerting on < 20 is correct.

3. Final Answer:

   if (RequestHandlerAvgIdlePercent < 20) { alert('High broker load'); } -> Option B

4. Quick Check:

   Idle percent < 20 means high load [OK]

Hint: Alert when idle percent is less than threshold [OK]

Common Mistakes:

• Using greater than instead of less than
• Checking equality only
• Using not equal which triggers too often