Merge pull request #2451 from MicrosoftDocs/main638681543586493770sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

data-explorer/kusto/api/connection-strings/storage-connection-strings.md

@@ -3,13 +3,13 @@ title:  Storage connection strings
 description: This article describes storage connection strings.
 ms.reviewer: shanisolomon
 ms.topic: reference
-ms.date: 08/11/2024
+ms.date: 11/19/2024
 ---
 # Storage connection strings
 
 > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)]
 
-The kusto service can interact with external storage services. For example, you can [create an Azure Storage external tables](../../management/external-tables-azure-storage.md) in order to query data stored on external storages.
+The Kusto service can interact with external storage services. For example, you can [create an Azure Storage external tables](../../management/external-tables-azure-storage.md) in order to query data stored on external storages.
 
 The following types of external storage are supported:
 
@@ -145,3 +145,10 @@ Use the [S3 presigned URL](https://docs.aws.amazon.com/AmazonS3/latest/userguide
 | Example |
 |--|
 | `"https://yourbucketname.s3.us-east-1.amazonaws.com/file.csv?12345678PRESIGNEDTOKEN"` |
+
+## Related Content
+
+For examples of how storage connection strings are used, see:
+
+* [externaldata operator](../../query/externaldata-operator.md)
+* [Create and alter Azure Storage external tables](../../management/external-tables-azure-storage.md).

data-explorer/kusto/management/query-consistency-policy.md

@@ -3,7 +3,7 @@ title: Query consistency policy
 description: Learn how to use the query consistency policy to control the consistency mode of queries.
 ms.reviewer: yonil
 ms.topic: reference
-ms.date: 08/11/2024
+ms.date: 11/20/2024
 ---
 # Query consistency policy
 
@@ -47,6 +47,12 @@ The following limits are configurable:
 }
 ```
 
+::: moniker range="azure-data-explorer"
+## Monitoring
+
+You can monitor the latency of the metadata snapshot age on nodes serving as weak consistency service heads by using the `Weak consistency latency` metric. For more information, see [Query metrics](/azure/data-explorer/using-metrics#query-metrics).
+::: moniker-end
+
 ## Related content
 
 * [.show workload_group command](show-workload-group-command.md)

data-explorer/using-metrics.md

@@ -3,7 +3,7 @@ title: Monitor Azure Data Explorer performance, health & usage with metrics
 description: Learn how to use Azure Data Explorer metrics to monitor the cluster's performance, health, and usage.
 ms.reviewer: gabil
 ms.topic: how-to
-ms.date: 09/10/2024
+ms.date: 11/20/2024
 ---
 
 # Monitor Azure Data Explorer performance, health, and usage with metrics
@@ -131,6 +131,7 @@ Query performance metrics track query duration and total number of concurrent or
 | QueryResult |	Count | Count | The total number of queries. |	QueryStatus | 
 | Total number of concurrent queries | Count | Avg, Max, Min, Sum | The number of queries run in parallel in the cluster. This metric is a good way to estimate the load on the cluster. | None |
 | Total number of throttled queries | Count | Avg, Max, Min, Sum | The number of throttled (rejected) queries in the cluster. The maximum number of concurrent (parallel) queries allowed is defined in the request rate limit policy. | None |
+| Weak consistency latency | Milliseconds | Avg, Max, Min | The age of the metadata snapshot used by nodes running the weak consistency service. | Database, Node |
 
 ## Materialized view metrics