Alert thresholds and policies in MLOps - Mini Project: Build & Apply

Alert thresholds and policies

📖 Scenario: You work in a machine learning operations (MLOps) team. Your job is to monitor model performance metrics and set alert thresholds. When a metric crosses a threshold, an alert policy triggers a notification.This helps the team quickly fix problems before they affect users.

🎯 Goal: Build a simple alert system that stores model metrics, sets threshold values, checks which metrics exceed thresholds, and prints alerts.

📋 What You'll Learn

Create a dictionary called model_metrics with exact keys and float values for metrics

Create a dictionary called alert_thresholds with exact keys matching metrics and float threshold values

Write a for loop using metric and value to check if each metric exceeds its threshold

Print alert messages for metrics that exceed thresholds exactly as specified

💡 Why This Matters

🌍 Real World

Monitoring machine learning model metrics helps catch problems early and maintain good performance in production.

💼 Career

MLOps engineers and DevOps teams use alert thresholds and policies to automate monitoring and incident response.

1

Create model metrics dictionary

Create a dictionary called model_metrics with these exact entries: 'accuracy': 0.92, 'precision': 0.85, 'recall': 0.72, 'f1_score': 0.77

MLOps

# Create the model_metrics dictionary with exact metric values
# Your code here

Hint

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

2

Set alert thresholds

Create a dictionary called alert_thresholds with these exact entries: 'accuracy': 0.90, 'precision': 0.80, 'recall': 0.75, 'f1_score': 0.78

MLOps

model_metrics = {'accuracy': 0.92, 'precision': 0.85, 'recall': 0.72, 'f1_score': 0.77}
# Create the alert_thresholds dictionary with exact threshold values
# Your code here

Hint

Use a dictionary to store the threshold values with the exact keys matching model_metrics.

3

Check metrics against thresholds

Write a for loop using variables metric and value to iterate over model_metrics.items(). Inside the loop, check if value is less than the corresponding threshold in alert_thresholds for that metric. If yes, add the metric to a list called alerts. Initialize alerts as an empty list before the loop.

MLOps

model_metrics = {'accuracy': 0.92, 'precision': 0.85, 'recall': 0.72, 'f1_score': 0.77}
alert_thresholds = {'accuracy': 0.90, 'precision': 0.80, 'recall': 0.75, 'f1_score': 0.78}
# Initialize alerts list
# Write a for loop to check each metric value against its threshold
# Your code here

Hint

Use model_metrics.items() to get metric and value pairs. Compare value with alert_thresholds[metric]. Add metric to alerts if below threshold.

4

Print alert messages

Write a for loop using variable metric to iterate over the alerts list. Inside the loop, print the message exactly as: "Alert: {metric} is below threshold!" where {metric} is replaced by the metric name.

MLOps

model_metrics = {'accuracy': 0.92, 'precision': 0.85, 'recall': 0.72, 'f1_score': 0.77}
alert_thresholds = {'accuracy': 0.90, 'precision': 0.80, 'recall': 0.75, 'f1_score': 0.78}
alerts = []
for metric, value in model_metrics.items():
    if value < alert_thresholds[metric]:
        alerts.append(metric)
# Print alert messages for each metric in alerts
# Your code here

Hint

Use a for loop to print each alert message exactly as shown, using an f-string.

Practice

1. What is the main purpose of setting an alert threshold in MLOps monitoring?

easy

A. To group multiple alerts into a single notification

B. To specify when a warning or alert should be triggered based on metric values

C. To define the actions taken after an alert is triggered

D. To store historical data of model performance

Solution

1. Step 1: Understand alert threshold concept

   An alert threshold sets a limit on a metric value that, when crossed, triggers an alert.

2. Step 2: Differentiate from policies and actions

   Policies group conditions and actions, but thresholds specifically define when alerts fire.

3. Final Answer:

   To specify when a warning or alert should be triggered based on metric values -> Option B

4. Quick Check:

   Alert threshold = trigger point [OK]

Hint: Thresholds set alert trigger points based on metrics [OK]

Common Mistakes:

• Confusing thresholds with alert grouping
• Thinking thresholds define actions
• Assuming thresholds store data

2. Which of the following is the correct way to define an alert threshold for CPU usage exceeding 80% in a YAML policy?

easy

A. threshold: { metric: 'cpu_usage', operator: '>', value: 80 }

B. threshold: { metric: 'cpu_usage', operator: '<', value: 80 }

C. threshold: { metric: 'cpu_usage', operator: '=', value: 80 }

D. threshold: { metric: 'cpu_usage', operator: '!=', value: 80 }

Solution

1. Step 1: Identify the correct operator for exceeding 80%

   Exceeding means greater than, so operator should be '>'.

2. Step 2: Match metric and value correctly

   Metric is 'cpu_usage' and value is 80, so the syntax matches threshold: { metric: 'cpu_usage', operator: '>', value: 80 }.

3. Final Answer:

   threshold: { metric: 'cpu_usage', operator: '>', value: 80 } -> Option A

4. Quick Check:

   Exceeding 80% means operator '>' [OK]

Hint: Use '>' operator for thresholds exceeding a value [OK]

Common Mistakes:

• Using '<' instead of '>' for exceeding
• Using '=' which triggers only at exact value
• Using '!=' which triggers for all except exact

3. Given this alert policy snippet:

thresholds:
  - metric: 'latency'
    operator: '>'
    value: 200
actions:
  - notify: 'on-call-team'

What happens when latency reaches 250?

medium

A. The alert triggers but no notification is sent

B. No alert is triggered because 250 is less than 200

C. An alert is triggered and the on-call team is notified

D. The system ignores latency metric

Solution

1. Step 1: Analyze threshold condition

   The threshold triggers when latency > 200. Since 250 > 200, condition is met.

2. Step 2: Check actions on trigger

   Action is to notify 'on-call-team', so notification will be sent.

3. Final Answer:

   An alert is triggered and the on-call team is notified -> Option C

4. Quick Check:

   Latency 250 > 200 triggers alert and notify [OK]

Hint: Check if metric value crosses threshold to trigger alerts [OK]

Common Mistakes:

• Misreading operator direction
• Ignoring actions linked to alerts
• Assuming no notification without explicit command

4. You have this alert policy configuration:

thresholds:
  - metric: 'error_rate'
    operator: '>'
    value: 5
actions:
  - notify: 'dev-team'

But alerts never trigger even when error_rate is 10. What is the likely issue?

medium

A. The operator should be '<' instead of '>'

B. Notifications require a separate enable flag

C. The value 5 is too high to trigger alerts

D. The metric name might be misspelled or mismatched

Solution

1. Step 1: Verify operator and value logic

   Operator '>' with value 5 means alert triggers if error_rate > 5, so 10 should trigger alert.

2. Step 2: Check metric name correctness

   If alerts never trigger, a common cause is metric name mismatch or typo causing no data match.

3. Final Answer:

   The metric name might be misspelled or mismatched -> Option D

4. Quick Check:

   Metric name mismatch blocks alert triggers [OK]

Hint: Check metric names carefully if alerts don't trigger [OK]

Common Mistakes:

• Changing operator incorrectly
• Assuming threshold value is too high
• Forgetting to enable notifications

5. You want to create a policy that triggers an alert if either model accuracy drops below 90% or latency exceeds 300ms. Which configuration correctly defines this combined alert policy?

hard

A. thresholds:
- metric: 'accuracy'
operator: '<'
value: 90
- metric: 'latency'
operator: '>'
value: 300
actions:
- notify: 'ml-team'

B. thresholds:
- metric: 'accuracy'
operator: '>'
value: 90
- metric: 'latency'
operator: '<'
value: 300
actions:
- notify: 'ml-team'

C. thresholds:
- metric: 'accuracy'
operator: '<'
value: 90
condition: 'AND'
- metric: 'latency'
operator: '>'
value: 300
actions:
- notify: 'ml-team'

D. thresholds:
- metric: 'accuracy'
operator: '<'
value: 90
condition: 'OR'
- metric: 'latency'
operator: '>'
value: 300
actions:
- notify: 'ml-team'

Solution

1. Step 1: Identify correct operators for conditions

   Accuracy below 90% means operator '<', latency exceeding 300 means operator '>'.

2. Step 2: Understand default logical grouping

   Most alert systems treat multiple thresholds as OR by default, so listing both triggers alert if either condition is met.

3. Step 3: Verify options for logical conditions

   Configurations that include a condition key (like 'OR' or 'AND') under a threshold are typically not valid syntax. The configuration using operator '>' for accuracy and '<' for latency has incorrect operators.

4. Final Answer:

   thresholds: - metric: 'accuracy' operator: '<' value: 90 - metric: 'latency' operator: '>' value: 300 actions: - notify: 'ml-team' -> Option A

5. Quick Check:

   Correct operators + default OR logic = thresholds: - metric: 'accuracy' operator: '<' value: 90 - metric: 'latency' operator: '>' value: 300 actions: - notify: 'ml-team' [OK]

Hint: Use correct operators and list thresholds for OR logic [OK]

Common Mistakes:

• Using wrong operators for conditions
• Adding unsupported 'condition' keys
• Assuming AND logic without explicit config