From 4c3a065ae9ae6a6c4c79af18a2839077043e8191 Mon Sep 17 00:00:00 2001
From: deefreak <69783777+deefreak@users.noreply.github.com>
Date: Wed, 17 Jan 2024 11:43:22 +0530
Subject: [PATCH 1/2] Update INSTALLATION.md

---
 INSTALLATION.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/INSTALLATION.md b/INSTALLATION.md
index 250c4bd..40e30da 100644
--- a/INSTALLATION.md
+++ b/INSTALLATION.md
@@ -7,7 +7,13 @@ Ottoscalr can be installed in any kubernetes cluster which meets the prerequisit
 - Kubernetes cluster (1.24+)
 - kube state metrics (2.8+)
 - Promql compliant metrics source (with historical workload utilization metrics)
+- Kube Prometheus (0.11+)
 
+## Prometheus metrics required 
+
+For ottoscalr to scrap cpu utilization data, cpu redline breach data and pod ready time data, certain metrics should be present in your Promql complaint metrics source. Go through all the [metrics](https://github.com/flipkart-incubator/ottoscalr/wiki/Recommenders#metrics-required) list. These metrics are required for ottoscalr to function. 
+
+Based on the above metrics, these are the [promql queries](https://github.com/flipkart-incubator/ottoscalr/wiki/Recommenders#promql-queries) that scrap cpu utilization data, cpu redline breach data and pod ready time data for a particular deployment. Do execute them in your Promql complaint metrics source to make sure that these queries provide the expected values. 
 
 ## Building the image
 

From a6741cf18469fe9bd9461261c38495571618dfd2 Mon Sep 17 00:00:00 2001
From: deefreak <69783777+deefreak@users.noreply.github.com>
Date: Wed, 17 Jan 2024 11:50:31 +0530
Subject: [PATCH 2/2] Update INSTALLATION.md

---
 INSTALLATION.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/INSTALLATION.md b/INSTALLATION.md
index 40e30da..aca5907 100644
--- a/INSTALLATION.md
+++ b/INSTALLATION.md
@@ -11,9 +11,9 @@ Ottoscalr can be installed in any kubernetes cluster which meets the prerequisit
 
 ## Prometheus metrics required 
 
-For ottoscalr to scrap cpu utilization data, cpu redline breach data and pod ready time data, certain metrics should be present in your Promql complaint metrics source. Go through all the [metrics](https://github.com/flipkart-incubator/ottoscalr/wiki/Recommenders#metrics-required) list. These metrics are required for ottoscalr to function. 
+For ottoscalr to scrap cpu utilization data, cpu redline breach data and pod ready time data, certain metrics should be present in your Promql complaint metrics source. Go through all the [metrics required](https://github.com/flipkart-incubator/ottoscalr/wiki/Metric-Sources#metrics-required) list. These metrics are required for ottoscalr to function. 
 
-Based on the above metrics, these are the [promql queries](https://github.com/flipkart-incubator/ottoscalr/wiki/Recommenders#promql-queries) that scrap cpu utilization data, cpu redline breach data and pod ready time data for a particular deployment. Do execute them in your Promql complaint metrics source to make sure that these queries provide the expected values. 
+Based on the above metrics, these are the [promql queries](https://github.com/flipkart-incubator/ottoscalr/wiki/Metric-Sources#promql-queries) that scrap cpu utilization data, cpu redline breach data and pod ready time data for a particular deployment. Do execute them in your Promql complaint metrics source to make sure that these queries provide the expected values. 
 
 ## Building the image