Skip to content

Commit 0178c23

Browse files
Merge pull request #257362 from b-ahibbard/crr-health
update alert rules
2 parents 1ff225f + 50beef6 commit 0178c23

File tree

2 files changed

+15
-20
lines changed

2 files changed

+15
-20
lines changed

articles/azure-netapp-files/cross-region-replication-display-health-status.md

Lines changed: 15 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ You can view replication status on the source volume or the destination volume.
3535
This is the state after you break the peering relationship. The destination volume is `‘RW’` and snapshots are present.
3636
* **Relationship status** – Shows one of the following values:
3737
* *Idle*:
38-
No transfer operation is in progress and future transfers are not disabled.
38+
No transfer operation is in progress and future transfers aren't disabled.
3939
* *Transferring*:
40-
A transfer operation is in progress and future transfers are not disabled.
40+
A transfer operation is in progress and future transfers aren't disabled.
4141
* **Replication schedule** – Shows how frequently incremental mirroring updates will be performed when the initialization (baseline copy) is complete.
4242

4343
* **Total progress** – Shows the total number of cumulative bytes transferred over the lifetime of the relationship. This amount is the actual bytes transferred, and it might differ from the logical space that the source and destination volumes report.
@@ -49,25 +49,20 @@ You can view replication status on the source volume or the destination volume.
4949
5050
## Set alert rules to monitor replication
5151

52-
Follow the following steps to create [alert rules in Azure Monitor](../azure-monitor/alerts/alerts-overview.md) to help you monitor the status of cross-region replication:
52+
Create [alert rules in Azure Monitor](../azure-monitor/alerts/alerts-overview.md) to help you monitor the status of cross-region replication:
5353

54-
1. From Azure Monitor, select **Alerts**.
55-
2. From the Alerts window, select the **Create** dropdown and select **Create new alert rule**.
56-
3. From the Scope tab of the Create an Alert Rule page, select **Select scope**. The **Select a Resource** page appears.
57-
4. From the Resource tab, find the **Volumes** resource type.
58-
5. From the Condition tab, select **Add condition**. From there, find a signal called “**is volume replication healthy**”.
59-
6. There you'll see **Condition of the relationship, 1 or 0** and the **Configure Signal Logic** window is displayed.
60-
7. To check if the replication is _unhealthy_:
61-
* Set **Operator** to `Less than`.
62-
* Set **Aggregation type** to `Average`.
63-
* Set **Threshold** value to `1`.
64-
* Set **Unit** to `Count`.
65-
8. To check if the replication is _healthy_:
66-
* Set **Operator** to `Greater than or equal to`.
67-
* Set **Aggregation** type to `Average`.
68-
* Set **Threshold** value to `1`.
69-
* Set **Unit** to `Count`.
70-
9. Select **Review + create**. The alert rule is ready for use.
54+
1. In Azure Monitor, select **Alerts**.
55+
2. From the **Alerts** window, select the **Create** dropdown then **Alert rule**.
56+
3. From the **Scope** tab of the **Create an Alert Rule** page, choose **Select scope**. The **Select a Resource** page appears.
57+
4. From the **Browse** tab, enter "Volumes" in the **Search to filter items...** field.
58+
5. Select the target volume you'd like to monitor and select **Apply**.
59+
6. From the **Condition** tab, use the **Signal name** dropdown to select **See all signals**. Identify the **Volume replication lag time** signal then select **Apply**.
60+
7. Confirm **Greater than** is selected for the **Operator** field.
61+
8. For the **Threshold** value field, enter the number of seconds equal to your replication schedule plus 20%. For example:
62+
* If your replication schedule is 10 minutes, enter 720 (10 minutes * 60 seconds * 1.2).
63+
* If your replication schedule is hourly, enter 4,320 (60 minutes * 60 seconds * 1.2).
64+
* If your replication schedule is daily, enter 103,680 (24 hours * 60 minutes * 60 seconds * 1.2).
65+
9. Select **Review + create**. The alert rule is ready for use.
7166

7267
:::image type="content" source="../media/azure-netapp-files/alert-config-signal-logic.png" alt-text="Screenshot of the Azure interface that shows the configure signal logic step with a backdrop of the Create alert rule page." lightbox="../media/azure-netapp-files/alert-config-signal-logic.png":::
7368

-562 KB
Loading

0 commit comments

Comments
 (0)