Merge pull request #295564 from normesta/normesta-reg-updates-14

Getting this in for Ozge

Author: prmerger-automator[bot]

articles/storage/blobs/monitor-blob-storage-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Monitoring data reference for Azure Blob Storage
 description: This article contains important reference material you need when you monitor Azure Blob Storage.
-ms.date: 11/05/2024
+ms.date: 02/27/2025
 ms.custom: horz-monitor
 ms.topic: reference
 author: normesta
@@ -23,6 +23,13 @@ The following table lists the metrics available for the Microsoft.Storage/storag
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
 [!INCLUDE [Microsoft.Storage/storageAccounts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-storage-storageaccounts-metrics-include.md)]
 
+### Category: Object replication
+
+| **Metric** | **Name in REST API** | **Unit** | **Aggregation** | **Dimensions** | **Time Grains** | **DS Export** |
+|---|---|---|---|---|---|---|
+| **Pending Bytes for Replication (preview)**<br><br>The size in bytes of the blob object pending for replication. | PendingBytesForReplication | Bytes | Average<br>Minimum, Maximum | TimeBucket, AccountName, and PolicyId | PT2M | No |
+| **Pending Operations for Replication (preview)**<br><br>The count of pending operations for replication. | PendingOperationsForReplication | Count | Average<br>Minimum, Maximum | TimeBucket, AccountName, and PolicyId | PT2M | No |
+
 ### Supported metrics for Microsoft.Storage/storageAccounts/blobServices
 The following table lists the metrics available for the Microsoft.Storage/storageAccounts/blobServices resource type.
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]

articles/storage/blobs/object-replication-configure.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 05/05/2022
+ms.date: 02/27/2025
 ms.author: normesta
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ---
@@ -215,6 +215,10 @@ az storage account or-policy show \
     --policy "@-"
 ```
 
+### [REST API](#tab/rest-api)
+
+N/A
+
 ---
 
 ## Configure object replication using a JSON file
@@ -228,7 +232,7 @@ For information about how to author a JSON file that contains the policy definit
 
 The examples in this section show how to configure the object replication policy on the destination account, and then get the JSON file for that policy that another user can use to configure the policy on the source account.
 
-# [Azure portal](#tab/portal)
+### [Azure portal](#tab/portal)
 
 To configure object replication on the destination account with a JSON file in the Azure portal, follow these steps:
 
@@ -257,7 +261,7 @@ The downloaded JSON file includes the policy ID that Azure Storage created for t
 
 Keep in mind that uploading a JSON file to create a replication policy for the destination account via the Azure portal doesn't automatically create the same policy in the source account. Another user must create the policy on the source account before Azure Storage begins replicating objects.
 
-# [PowerShell](#tab/powershell)
+### [PowerShell](#tab/powershell)
 
 To download a JSON file that contains the replication policy definition for the destination account from PowerShell, call the [Get-AzStorageObjectReplicationPolicy](/powershell/module/az.storage/get-azstorageobjectreplicationpolicy) command to return the policy. Then convert the policy to JSON and save it as a local file, as shown in the following example. Remember to replace values in angle brackets and the file path with your own values:
 
@@ -284,7 +288,7 @@ Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -Rule $object.Rules
 ```
 
-# [Azure CLI](#tab/azure-cli)
+### [Azure CLI](#tab/azure-cli)
 
 To write the replication policy definition for the destination account to a JSON file from Azure CLI, call the [az storage account or-policy show](/cli/azure/storage/account/or-policy#az-storage-account-or-policy-show) command and output to a file.
 
@@ -305,13 +309,68 @@ az storage account or-policy create \
     --policy @policy.json
 ```
 
+### [REST API](#tab/rest-api)
+
+N/A
+
+---
+
+## Configure replication metrics
+
+### Enable replication metrics
+
+You can enable replication metrics on both new and existing object replication policies. It might take a few minutes to start observing the metrics.  
+
+#### [Azure portal](#tab/portal)
+
+You can enable metrics using **Object Replication** blade from the new _Metrics_ column or by editing the _Edit Rules_ section of a policy from "…" on the OR policy row.
+
+#### [PowerShell](#tab/powershell)
+
+Not yet supported.
+
+#### [Azure CLI](#tab/azure-cli)
+
+Not yet supported.
+
+#### [REST API](#tab/rest-api)
+
+Enabling metrics is supported on API version 2021-08-01 and above. You can add the new metrics field to the replication policy. Sample: 
+
+``` json
+{
+    "sourceAccount": "<source-account-name>",
+    "destinationAccount": "<destination-account-name>",
+    "metrics":
+    {
+     "enabled": true
+    },
+    "rules":
+    [
+        {
+            "ruleId": "<rule-id>",
+            "sourceContainer": "<source-container-name>",
+            "destinationContainer": "<destination-container-name>"
+        }
+    ]
+}
+```
+
 ---
 
+If you enable metrics on a policy that is configured to copy over existing data, you might observe an increasing amount at the beginning while the policy works on initial phase of listing. Once this is completed, the replication will start.
+
+### View replication metrics
+
+You can click the **View** link from Metrics column to view monitoring metrics
+
+To further view metrics in Azure Monitor, click on chart of a metric. This will direct you to Azure Monitor Metrics view with more filtering capabilities.
+
 ## Check the replication status of a blob
 
 You can check the replication status for a blob in the source account using the Azure portal, PowerShell, or Azure CLI. Object replication properties aren't populated until replication has either completed or failed.
 
-# [Azure portal](#tab/portal)
+### [Azure portal](#tab/portal)
 
 To check the replication status for a blob in the source account in the Azure portal, follow these steps:
 
@@ -321,7 +380,7 @@ To check the replication status for a blob in the source account in the Azure po
 
 :::image type="content" source="media/object-replication-configure/check-replication-status-source.png" alt-text="Screenshot showing replication status for a blob in the source account":::
 
-# [PowerShell](#tab/powershell)
+### [PowerShell](#tab/powershell)
 
 To check the replication status for a blob in the source account with PowerShell, get the value of the object replication **ReplicationStatus** property, as shown in the following example. Remember to replace values in angle brackets with your own values:
 
@@ -334,7 +393,7 @@ $blobSrc = Get-AzStorageBlob -Container $srcContainerName1 `
 $blobSrc.BlobProperties.ObjectReplicationSourceProperties[0].Rules[0].ReplicationStatus
 ```
 
-# [Azure CLI](#tab/azure-cli)
+### [Azure CLI](#tab/azure-cli)
 
 To check the replication status for a blob in the source account with Azure CLI, get the value of the object replication **status** property, as shown in the following example:
 
@@ -348,19 +407,23 @@ az storage blob show \
     --auth-mode login
 ```
 
----
-
 If the replication status for a blob in the source account indicates failure, then investigate the following possible causes:
 
 - Make sure that the object replication policy is configured on the destination account.
 - Verify that the destination container still exists.
 - If the source blob has been encrypted with a customer-provided key as part of a write operation, then object replication will fail. For more information about customer-provided keys, see [Provide an encryption key on a request to Blob storage](encryption-customer-provided-keys.md).
 
+### [REST API](#tab/rest-api)
+
+N/A
+
+---
+
 ## Remove a replication policy
 
 To remove a replication policy and its associated rules, use Azure portal, PowerShell, or CLI.
 
-# [Azure portal](#tab/portal)
+### [Azure portal](#tab/portal)
 
 To remove a replication policy in the Azure portal, follow these steps:
 
@@ -369,7 +432,7 @@ To remove a replication policy in the Azure portal, follow these steps:
 1. Select the **More** button next to the policy name.
 1. Select **Delete Rules**.
 
-# [PowerShell](#tab/powershell)
+### [PowerShell](#tab/powershell)
 
 To remove a replication policy, delete the policy from both the source account and the destination account. Deleting the policy also deletes any rules associated with it.
 
@@ -385,7 +448,7 @@ Remove-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -PolicyId $destPolicy.PolicyId
 ```
 
-# [Azure CLI](#tab/azure-cli)
+### [Azure CLI](#tab/azure-cli)
 
 To remove a replication policy, delete the policy from both the source account and the destination account. Deleting the policy also deletes any rules associated with it.
 
@@ -401,6 +464,10 @@ az storage account or-policy delete \
     --resource-group <resource-group>
 ```
 
+### [REST API](#tab/rest-api)
+
+N/A
+
 ---
 
 ## Next steps

articles/storage/blobs/object-replication-overview.md

@@ -6,8 +6,8 @@ author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: conceptual
-ms.date: 12/08/2023
-ms.author: nachakra
+ms.date: 02/27/2025
+ms.author: normesta
 ms.custom: engagement-fy23
 ---
 
@@ -191,6 +191,31 @@ By default, the **AllowCrossTenantReplication** property is set to false for a s
 
 You can use Azure Policy to audit a set of storage accounts to ensure that the **AllowCrossTenantReplication** property is set to prevent cross-tenant object replication. You can also use Azure Policy to enforce governance for a set of storage accounts. For example, you can create a policy with the deny effect to prevent a user from creating a storage account where the **AllowCrossTenantReplication** property is set to *true*, or from modifying an existing storage account to change the property value to *true*.
 
+## Replication metrics
+> [!IMPORTANT]
+> Object replication metrics is currently in PREVIEW and available in all regions.
+> To opt in to the preview, see [Set up preview features in Azure subscription](/azure/azure-resource-manager/management/preview-features.md) and specify AllowObjectReplicationMetrics as the feature name. The provider name for this preview feature is Microsoft.Storage.
+> 
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+Object replication supports two metrics to provide you with insights into the replication progress:
+
+- **Operations pending for replication**: Total number of operations pending replication from source to destination storage account emitted per the time buckets
+- **Bytes pending for replication**: Sum of bytes pending replication from source to destination storage accounts emitted per the time buckets
+
+Each of the metrics above can be viewed with the dimension of time buckets. This enables insights into how many bytes or operations are pending for replication per time buckets as follows:
+
+- 0-5 mins
+- 5-10 mins
+- 10-15 mins
+- 15-30 mins
+- 30 mins-2 hrs
+- 2-8 hrs
+- 8-24 hrs
+- `>`24 hrs  
+
+You can enable replication metrics on the source account for monitoring pending bytes and pending operations. For more information, see [Configure replication metrics](object-replication-configure.md#configure-replication-metrics).
+
 ## Replication status
 
 You can check the replication status for a blob in the source account. For more information, see [Check the replication status of a blob](object-replication-configure.md#check-the-replication-status-of-a-blob).