diff --git a/docs/track-metrics-using-kubeflow.md b/docs/track-metrics-using-kubeflow.md
new file mode 100644
index 0000000..be35db3
--- /dev/null
+++ b/docs/track-metrics-using-kubeflow.md
@@ -0,0 +1,79 @@
+# Experiment tracking using Kubeflow Pipelines
+
+[![Experiment Tracking](https://img.youtube.com/vi/mZ98f9TWDCk/0.jpg)](https://youtu.be/mZ98f9TWDCk)
+
+In this guide you will learn how to use kubeflow pipelines to track metrics from different experiments and runs.
+
+[Kubeflow Pipelines](https://www.kubeflow.org/docs/components/pipelines/) is a platform for building and deploying scalable machine learning (ML) workflows. It allows us to automate the running of  jupyter notebooks and scripts using a simple workflow. Using Kubeflow pipelines we can automate the running of multiple steps of a ML pipeline like data collection, model training, inference, and control which steps need to be performed sequentially and which should run in  parallel.
+ 
+Kubeflow pipelines also allow us to [export metrics](https://www.kubeflow.org/docs/components/pipelines/sdk/pipelines-metrics/) from a running pipeline. This helps us compare multiple runs over multiple model training runs. We can also compare the achieved model performance metrics like accuracy, f1, etc.
+
+## Pre-requisites
+
+1. Existing kubeflow pipeline instance available and the components (notebooks or scripts) that you want to track metrics for.
+
+_For a guide on how to create an pipeline using Elyra, Kubeflow pipelines check out this [video](https://youtu.be/iMSOal8wRj4)_
+
+
+## Track Metrics
+
+To enable tracking of metrics during the execution of a machine learning experiment, your component must have an output called `mlpipeline-metrics`  which must return a JSON-serialized metrics dictionary. Let's demonstrate this with the help of an example.
+
+Below we will demonstrate how to capture metrics for the time taken to execute certain queries, and the time taken to upload some files to S3 storage.
+
+1. Declare a file where you want to store the captured metrics. It must be named `mlpipeline-metrics.json`.
+
+```
+# file to store runtime kfpipeline metrics
+metrics_file_path = './mlpipeline-metrics.json'
+```
+
+2. Initialize variables which capture metrics such as time taken to execute certain parts of the code. In the following lines of code, we capture the time taken to upload `emissions_table1.parquet` onto S3 as `upload_df1_time`.
+
+```
+df_emissions.to_parquet("/tmp/emissions_table1.parquet", index=False)
+t = time.time()
+s3.upload_file(
+    Bucket=os.environ["S3_BUCKET"],
+    Key="urgentem/trino/itr_emissions_join_1/emissions.parquet",
+    Filename="/tmp/emissions_table1.parquet",
+)
+upload_df1_time = time.time() - t
+```
+
+3. Aggregate all the metrics captured within the notebook into a dictionary called `metrics` and export the json-serialized metrics dictionary into the `mlpipeline-metrics` file.
+
+```
+metrics = {
+    "metrics":[
+        {
+            "name":"no_rows_emissions_table_1",
+            "numberValue":len_emssions_data_1,
+            "format":"RAW"
+        },
+        {
+            "name":"no_rows_emissions_table_2",
+            "numberValue":len_emssions_data_2,
+            "format":"RAW"
+        },
+        {
+            "name":"time_to_upload_df_1",
+            "numberValue":upload_df1_time,
+            "format":"RAW"
+        }
+    ]
+}
+```
+4. Once the notebook is  configured to track metrics and the pipeline has been submitted, you can move over to the kubeflow UI to view the metrics that are being captured during notebook run.
+
+![metrics](../public/assets/track-metrics-using-kubeflow/metrics.png)
+
+By clicking on a particular run, and moving over to the `Run output` tab, you can view the metrics captured for each notebook during the particular run.
+
+5. To compare runs, from the experiments tab, you can select multiple runs and click on "Compare Runs" on the top right. This will show a table comparing the metrics capture during the selected runs.
+
+This can be especially helpful while tracking multiple model training runs, and can be used to capture model performance metrics.
+
+![metrics](../public/assets/track-metrics-using-kubeflow/compare-runs.png)
+
+If you want to see an real example of how to integrate experiement tracking, take a look at this [notebook](https://github.com/os-climate/aicoe-osc-demo/blob/master/notebooks/demo1/demo1-create-tables.ipynb).
\ No newline at end of file
diff --git a/public/assets/track-metrics-using-kubeflow/compare-runs.png b/public/assets/track-metrics-using-kubeflow/compare-runs.png
new file mode 100644
index 0000000..6f3633d
Binary files /dev/null and b/public/assets/track-metrics-using-kubeflow/compare-runs.png differ
diff --git a/public/assets/track-metrics-using-kubeflow/metrics.png b/public/assets/track-metrics-using-kubeflow/metrics.png
new file mode 100644
index 0000000..43f10ef
Binary files /dev/null and b/public/assets/track-metrics-using-kubeflow/metrics.png differ