From 184238ecd30eedb279b0f58eaf552b94b95e2b8c Mon Sep 17 00:00:00 2001 From: Neelanjan Manna Date: Sat, 24 Sep 2022 23:45:22 +0530 Subject: [PATCH] fix: Corrected Typographical Error in Azure Log Analytics Scaler Docs (#944) --- content/docs/2.0/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.1/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.2/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.3/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.4/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.5/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.6/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.7/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.8/scalers/azure-log-analytics.md | 4 ++-- content/docs/2.9/scalers/azure-log-analytics.md | 4 ++-- 10 files changed, 20 insertions(+), 20 deletions(-) diff --git a/content/docs/2.0/scalers/azure-log-analytics.md b/content/docs/2.0/scalers/azure-log-analytics.md index a2e36464dca..b300d69ef91 100755 --- a/content/docs/2.0/scalers/azure-log-analytics.md +++ b/content/docs/2.0/scalers/azure-log-analytics.md @@ -79,7 +79,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -119,7 +119,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.1/scalers/azure-log-analytics.md b/content/docs/2.1/scalers/azure-log-analytics.md index cdc6d19f0b9..4e37c96f6d4 100644 --- a/content/docs/2.1/scalers/azure-log-analytics.md +++ b/content/docs/2.1/scalers/azure-log-analytics.md @@ -79,7 +79,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -119,7 +119,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.2/scalers/azure-log-analytics.md b/content/docs/2.2/scalers/azure-log-analytics.md index cdc6d19f0b9..4e37c96f6d4 100644 --- a/content/docs/2.2/scalers/azure-log-analytics.md +++ b/content/docs/2.2/scalers/azure-log-analytics.md @@ -79,7 +79,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -119,7 +119,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.3/scalers/azure-log-analytics.md b/content/docs/2.3/scalers/azure-log-analytics.md index cdc6d19f0b9..4e37c96f6d4 100644 --- a/content/docs/2.3/scalers/azure-log-analytics.md +++ b/content/docs/2.3/scalers/azure-log-analytics.md @@ -79,7 +79,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -119,7 +119,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.4/scalers/azure-log-analytics.md b/content/docs/2.4/scalers/azure-log-analytics.md index cdc6d19f0b9..4e37c96f6d4 100644 --- a/content/docs/2.4/scalers/azure-log-analytics.md +++ b/content/docs/2.4/scalers/azure-log-analytics.md @@ -79,7 +79,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -119,7 +119,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.5/scalers/azure-log-analytics.md b/content/docs/2.5/scalers/azure-log-analytics.md index eee3ec8bd6b..ef85ac70c8e 100644 --- a/content/docs/2.5/scalers/azure-log-analytics.md +++ b/content/docs/2.5/scalers/azure-log-analytics.md @@ -80,7 +80,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -120,7 +120,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.6/scalers/azure-log-analytics.md b/content/docs/2.6/scalers/azure-log-analytics.md index eee3ec8bd6b..ef85ac70c8e 100644 --- a/content/docs/2.6/scalers/azure-log-analytics.md +++ b/content/docs/2.6/scalers/azure-log-analytics.md @@ -80,7 +80,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -120,7 +120,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.7/scalers/azure-log-analytics.md b/content/docs/2.7/scalers/azure-log-analytics.md index 6ed77127e5b..00f806f1fa6 100644 --- a/content/docs/2.7/scalers/azure-log-analytics.md +++ b/content/docs/2.7/scalers/azure-log-analytics.md @@ -89,7 +89,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -129,7 +129,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.8/scalers/azure-log-analytics.md b/content/docs/2.8/scalers/azure-log-analytics.md index ccd24a485ed..9849af0bcd2 100644 --- a/content/docs/2.8/scalers/azure-log-analytics.md +++ b/content/docs/2.8/scalers/azure-log-analytics.md @@ -91,7 +91,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -131,7 +131,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters diff --git a/content/docs/2.9/scalers/azure-log-analytics.md b/content/docs/2.9/scalers/azure-log-analytics.md index ccd24a485ed..9849af0bcd2 100644 --- a/content/docs/2.9/scalers/azure-log-analytics.md +++ b/content/docs/2.9/scalers/azure-log-analytics.md @@ -91,7 +91,7 @@ It is important to design your query to return 1 table with 1 row. A good practi Scaler will take value from: - 1st cell as Metrics Value. -- 2d cell as Threshold (optional). +- 2nd cell as Threshold (optional). You can define threshold in trigger metadata, it will be used if your query results only 1 cell, that will be interpreted as metric value. Be aware, even if you have defined threshold in metadata, it can be overwritten by your query. @@ -131,7 +131,7 @@ Example result: ### Scaler Limitations -- As it was mentioned before, you can define a threshold using query (2d cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. +- As it was mentioned before, you can define a threshold using query (2nd cell of query result will be interpret as threshold). Be aware! Threshold from query result will be set only once, during scaler creation. So, if your query will return different threshold values during runtime, they will not be propagated to Horizontal Pod Autoscaler target. ### Authentication Parameters