Skip to content

Commit

Permalink
fix: Corrected Typographical Error in Azure Log Analytics Scaler Docs (
Browse files Browse the repository at this point in the history
  • Loading branch information
neelanjan00 authored Sep 24, 2022
1 parent e67cadf commit 184238e
Show file tree
Hide file tree
Showing 10 changed files with 20 additions and 20 deletions.
4 changes: 2 additions & 2 deletions content/docs/2.0/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.1/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.2/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.3/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.4/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.5/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.6/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.7/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.8/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions content/docs/2.9/scalers/azure-log-analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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

Expand Down

0 comments on commit 184238e

Please sign in to comment.