Model metadata and lineage in MLOps - Step-by-Step Execution

Process Flow - Model metadata and lineage

Start: Model Created

↓

Capture Metadata

↓

Store Metadata

↓

Track Lineage

↓

Update Metadata & Lineage on Changes

↓

Use Metadata & Lineage for Audits/Debug

↓

End

The flow shows how model metadata is captured, stored, and lineage tracked through changes to support audits and debugging.

Execution Sample

MLOps

model = create_model('v1')
metadata = capture_metadata(model)
store_metadata(metadata)
lineage = track_lineage(model)
update_metadata(metadata, 'v2')
model = create_model('v2')
lineage = track_lineage(model)

This code creates a model, captures and stores its metadata, tracks lineage, then updates metadata for a new version and tracks lineage for the new model.

Process Table

Step	Action	Input	Output	System State Change
1	Create model	'v1'	Model object v1	Model instance created
2	Capture metadata	Model object v1	Metadata {version: 'v1', created_at: timestamp}	Metadata extracted from model
3	Store metadata	Metadata {version: 'v1', created_at: timestamp}	Stored in metadata DB	Metadata saved in database
4	Track lineage	Model object v1	Lineage record {parent: null, model: 'v1'}	Lineage entry created
5	Update metadata	Metadata, new version 'v2'	Metadata updated {version: 'v2', updated_at: timestamp}	Metadata record updated
6	Create model	'v2'	Model object v2	Model instance created
7	Track lineage	Model object v2	Lineage record {parent: 'v1', model: 'v2'}	Lineage updated with new version
8	Use metadata & lineage	Query metadata DB	Audit report generated	Audit completed
9	End	-	-	Process complete

💡 Process ends after metadata and lineage are updated and used for audit.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 7	Final
model	null	Model v1 object	Model v1 object	Model v1 object	Model v2 object	Model v2 object
metadata	null	null	{version: 'v1', created_at: timestamp}	{version: 'v2', updated_at: timestamp}	{version: 'v2', updated_at: timestamp}	{version: 'v2', updated_at: timestamp}
lineage	null	null	Lineage {parent: null, model: 'v1'}	Lineage {parent: null, model: 'v1'}	Lineage {parent: 'v1', model: 'v2'}	Lineage {parent: 'v1', model: 'v2'}

Key Moments - 3 Insights

Why do we track lineage after updating the model version?

Because lineage shows the relationship between model versions, tracking it after updates (see steps 5 and 7) helps understand model evolution.

What happens if metadata is not stored after capture?

If metadata is not stored (step 3), it cannot be used later for audits or debugging, breaking traceability.

How does metadata help in audits?

Metadata contains details like version and timestamps (step 8), which auditors use to verify model history and changes.

Visual Quiz - 3 Questions

Look at the execution table, what is the metadata version after step 5?

A 'v1'

B null

C 'v2'

D 'v3'

💡 Hint

Check the Output column at step 5 in the execution table.

At which step is the lineage first created?

A Step 2

B Step 4

C Step 7

D Step 3

💡 Hint

Look for 'Lineage entry created' in the System State Change column.

If we skip storing metadata at step 3, what is the likely impact?

A Audit reports cannot be generated properly

B Lineage tracking will fail

C Model creation will fail

D Metadata will update automatically

💡 Hint

Refer to the key moment about metadata storage and audit usage.

Concept Snapshot

Model metadata records details like version and timestamps.
Lineage tracks model relationships and changes over time.
Capture metadata when creating or updating models.
Store metadata and lineage in a database.
Use metadata and lineage for audits and debugging.
Keep lineage updated with each model version.

Full Transcript

This visual execution shows how model metadata and lineage are managed in MLOps. First, a model is created, then metadata is captured and stored. Lineage is tracked to record relationships between model versions. When the model updates, metadata and lineage are updated accordingly. Finally, metadata and lineage are used for audits and debugging. Variables like model, metadata, and lineage change step-by-step, showing how the system state evolves. Key moments clarify why lineage is tracked after updates, why storing metadata is essential, and how metadata supports audits. The quiz tests understanding of metadata versions, lineage creation steps, and the impact of skipping metadata storage.

Practice

1. What is the main purpose of model metadata in MLOps?

easy

A. To clean the input data before training

B. To execute the model training automatically

C. To deploy the model to production

D. To store important details about the model's creation and performance

Solution

1. Step 1: Understand what model metadata contains

   Model metadata includes details like training parameters, performance metrics, and environment info.

2. Step 2: Identify the purpose of metadata

   This information helps track how the model was created and how well it performs.

3. Final Answer:

   To store important details about the model's creation and performance -> Option D

4. Quick Check:

   Model metadata = model details storage [OK]

Hint: Metadata stores model info, not execution or deployment [OK]

Common Mistakes:

• Confusing metadata with deployment steps
• Thinking metadata runs the model
• Mixing metadata with data cleaning

2. Which of the following is the correct way to represent model lineage?

easy

A. A graph showing connections between data, code, and model versions

B. A list of model hyperparameters only

C. A single file containing the trained model weights

D. A script that trains the model

Solution

1. Step 1: Define model lineage

   Model lineage tracks the history and relationships between data, code, and model versions.

2. Step 2: Identify correct representation

   A graph or map showing these connections is the correct way to represent lineage.

3. Final Answer:

   A graph showing connections between data, code, and model versions -> Option A

4. Quick Check:

   Lineage = connection graph [OK]

Hint: Lineage means tracking history and connections [OK]

Common Mistakes:

• Thinking lineage is just model parameters
• Confusing lineage with model files
• Assuming lineage is a training script

3. Given the following metadata record:

{"model_version": "v1.2", "accuracy": 0.92, "training_data": "dataset_v3", "code_commit": "abc123"}

What does the code_commit field represent?

medium

A. The version of the training dataset used

B. The unique identifier of the code version used to train the model

C. The accuracy score of the model

D. The deployment environment name

Solution

1. Step 1: Analyze the metadata fields

   The field code_commit usually stores the code version identifier, like a git commit hash.

2. Step 2: Match field meaning to options

   It identifies the exact code used to train the model, ensuring reproducibility.

3. Final Answer:

   The unique identifier of the code version used to train the model -> Option B

4. Quick Check:

   code_commit = code version ID [OK]

Hint: Code commit means code version ID, not data or accuracy [OK]

Common Mistakes:

• Confusing code_commit with dataset version
• Thinking it stores accuracy
• Assuming it is deployment info

4. You notice that the model lineage graph is missing links between data versions and model versions. What is the most likely cause?

medium

A. The training code commit hash is missing

B. The model accuracy was too low

C. The metadata did not record the data version used during training

D. The deployment script failed to run

Solution

1. Step 1: Understand lineage graph links

   Links between data versions and model versions require metadata recording the data version used.

2. Step 2: Identify missing metadata impact

   If data version info is missing, lineage cannot connect data to model versions.

3. Final Answer:

   The metadata did not record the data version used during training -> Option C

4. Quick Check:

   Missing data version metadata breaks lineage links [OK]

Hint: Missing data version metadata breaks lineage connections [OK]

Common Mistakes:

• Blaming model accuracy for lineage issues
• Confusing deployment errors with lineage
• Assuming code commit missing causes data link loss

5. You want to ensure full reproducibility of your ML model training. Which combination of metadata and lineage tracking is best?

hard

A. Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph

B. Only save the final trained model file

C. Track deployment environment and ignore training data versions

D. Store training logs without linking to code or data versions

Solution

1. Step 1: Identify key elements for reproducibility

   Reproducibility requires knowing hyperparameters, data version, and exact code used.

2. Step 2: Understand lineage role

   Linking these elements in a lineage graph shows their relationships and history.

3. Step 3: Evaluate options

   Only Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph includes all necessary metadata and lineage tracking for full reproducibility.

4. Final Answer:

   Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph -> Option A

5. Quick Check:

   Full reproducibility = metadata + lineage graph [OK]

Hint: Combine metadata and lineage graph for full reproducibility [OK]

Common Mistakes:

• Saving only model files without metadata
• Ignoring data version tracking
• Not linking metadata in lineage