Logging parameters and metrics in MLOps - Mini Project: Build & Apply

Logging Parameters and Metrics in MLOps

📖 Scenario: You are working on a machine learning project. You want to keep track of the settings (parameters) you use and the results (metrics) you get. This helps you understand which settings work best.

🎯 Goal: Build a simple Python script that logs model parameters and metrics using a dictionary. You will create the data, add a configuration, log the main results, and then display the logged information.

📋 What You'll Learn

Create a dictionary called params with exact keys and values for model parameters

Create a dictionary called metrics with exact keys and values for model evaluation

Add a variable called experiment_name with a specific string value

Log the parameters and metrics into a single dictionary called log

Print the log dictionary to display all logged information

💡 Why This Matters

🌍 Real World

Logging parameters and metrics is essential in machine learning projects to track experiments and improve models over time.

💼 Career

Data scientists and MLOps engineers use logging to monitor model performance and reproduce results reliably.

1

Create model parameters dictionary

Create a dictionary called params with these exact entries: 'learning_rate': 0.01, 'batch_size': 32, 'optimizer': 'adam'.

MLOps

# Create the params dictionary with the given keys and values
# Your code here

Hint

Use curly braces {} to create a dictionary. Separate keys and values with a colon :.

2

Create model metrics dictionary and experiment name

Create a dictionary called metrics with these exact entries: 'accuracy': 0.85, 'loss': 0.35. Also create a variable called experiment_name and set it to the string 'exp_001'.

MLOps

params = {'learning_rate': 0.01, 'batch_size': 32, 'optimizer': 'adam'}
# Create the metrics dictionary with the given keys and values
# Create the experiment_name variable with the given string
# Your code here

Hint

Create another dictionary like params for metrics. Use a simple assignment for experiment_name.

3

Log parameters and metrics into a single dictionary

Create a dictionary called log that contains three keys: 'experiment' with the value of experiment_name, 'parameters' with the value of params, and 'metrics' with the value of metrics.

MLOps

params = {'learning_rate': 0.01, 'batch_size': 32, 'optimizer': 'adam'}
metrics = {'accuracy': 0.85, 'loss': 0.35}
experiment_name = 'exp_001'
# Create the log dictionary combining experiment_name, params, and metrics
# Your code here

Hint

Use a dictionary with keys pointing to the existing variables. For example, 'experiment': experiment_name.

4

Print the logged information

Write a print statement to display the log dictionary.

MLOps

params = {'learning_rate': 0.01, 'batch_size': 32, 'optimizer': 'adam'}
metrics = {'accuracy': 0.85, 'loss': 0.35}
experiment_name = 'exp_001'
log = {'experiment': experiment_name, 'parameters': params, 'metrics': metrics}
# Print the log dictionary
# Your code here

Hint

Use print(log) to show the logged data.

Practice

1.

What is the main purpose of logging parameters in machine learning experiments?

easy

A. To record the settings used during model training

B. To measure the model's accuracy on test data

C. To save the final trained model file

D. To visualize the model's predictions

Solution

1. Step 1: Understand what parameters are

   Parameters are the settings or configurations used to train a model, like learning rate or number of layers.

2. Step 2: Identify the purpose of logging parameters

   Logging parameters helps keep track of these settings so you can compare different training runs.

3. Final Answer:

   To record the settings used during model training -> Option A

4. Quick Check:

   Logging parameters = record training settings [OK]

Hint: Parameters = training settings, metrics = performance [OK]

Common Mistakes:

• Confusing parameters with metrics
• Thinking logging saves the model file
• Assuming logging is for visualization

2.

Which of the following is the correct way to log a metric named accuracy with value 0.95 using a typical MLOps logging function log_metric?

easy

A. log_metric('accuracy', 0.95)

B. log_metric(accuracy=0.95)

C. log_metric('accuracy': 0.95)

D. log_metric(0.95, 'accuracy')

Solution

1. Step 1: Understand typical function syntax

   Logging functions usually take the metric name as a string first, then the value as a number.

2. Step 2: Check each option's syntax

   log_metric('accuracy', 0.95) uses correct syntax: function name, string key, numeric value. log_metric(accuracy=0.95) uses keyword argument which may not be supported. log_metric('accuracy': 0.95) uses invalid syntax with colon inside parentheses. log_metric(0.95, 'accuracy') reverses arguments incorrectly.

3. Final Answer:

   log_metric('accuracy', 0.95) -> Option A

4. Quick Check:

   Function(metric_name, value) = correct syntax [OK]

Hint: Metric name first as string, then value [OK]

Common Mistakes:

• Using colon instead of comma in function call
• Passing arguments in wrong order
• Using keyword arguments when not supported

3.

Given the following code snippet, what will be the output logged for the metric loss?

log_metric('loss', 0.25)
log_metric('loss', 0.20)
log_metric('loss', 0.15)

medium

A. Only the last value 0.15 is logged for 'loss'

B. An error occurs because 'loss' is logged multiple times

C. All three values 0.25, 0.20, and 0.15 are logged separately

D. The first value 0.25 overwrites the others

Solution

1. Step 1: Understand metric logging behavior

   Most MLOps tools allow logging multiple values for the same metric over time to track progress.

2. Step 2: Analyze the code snippet

   The code logs 'loss' three times with different values. Each call records a new metric value, not overwriting previous ones.

3. Final Answer:

   All three values 0.25, 0.20, and 0.15 are logged separately -> Option C

4. Quick Check:

   Multiple logs for same metric = multiple entries [OK]

Hint: Repeated metric logs add entries, not overwrite [OK]

Common Mistakes:

• Assuming repeated logs overwrite previous values
• Expecting an error on duplicate metric names
• Thinking only one value per metric is allowed

4.

Identify the error in this code snippet for logging a parameter batch_size with value 32:

log_param(batch_size, '32')

medium

A. Function name should be log_metric instead of log_param

B. Value should be a number, not a string

C. No error, the code is correct

D. Parameter name should be a string, not a variable

Solution

1. Step 1: Check parameter name argument

   The parameter name must be a string literal like 'batch_size', not a bare variable name.

2. Step 2: Check value argument

   Value can be string or number depending on context; '32' as string is acceptable here.

3. Final Answer:

   Parameter name should be a string, not a variable -> Option D

4. Quick Check:

   Parameter name = string literal [OK]

Hint: Parameter names must be quoted strings [OK]

Common Mistakes:

• Passing parameter name without quotes
• Confusing log_param with log_metric
• Thinking value must always be numeric

5.

You want to log both parameters and metrics for a training run using the following code:

log_param('learning_rate', 0.01)
log_param('optimizer', 'adam')
log_metric('accuracy', 0.92)
log_metric('loss', 0.1)

Which of these statements is true about the logged data?

hard

A. Metrics record model settings; parameters record model performance

B. Parameters record model settings; metrics record model performance

C. Both parameters and metrics record model performance

D. Both parameters and metrics record model settings

Solution

1. Step 1: Understand the role of parameters

   Parameters like learning rate and optimizer are settings used to train the model.

2. Step 2: Understand the role of metrics

   Metrics like accuracy and loss measure how well the model performs after training.

3. Final Answer:

   Parameters record model settings; metrics record model performance -> Option B

4. Quick Check:

   Parameters = settings, Metrics = performance [OK]

Hint: Parameters = settings, metrics = results [OK]

Common Mistakes:

• Mixing up parameters and metrics roles
• Thinking metrics are settings
• Assuming parameters measure performance