Skip to content

Commit 5e7c3aa

Browse files
Merge pull request #222303 from AwdotiaRomanowna/patch-16
Update how-to-read-replicas-portal.md
2 parents 9ccb5a7 + 1bec943 commit 5e7c3aa

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/postgresql/flexible-server/how-to-read-replicas-portal.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,15 +131,13 @@ The **Max Physical Replication Lag** metric shows the lag in bytes between the p
131131
2. Select **Metrics**. In the **Metrics** window, select **Max Physical Replication Lag**.
132132

133133
:::image type="content" source="./media/how-to-read-replicas-portal/metrics_max_physical_replication_lag.png" alt-text="Screenshot of the Metrics blade showing Max Physical Replication Lag metric.":::
134-
135-
:::image-end:::
136134

137135
3. For your **Aggregation**, select **Max**.
138136

139137
### Read Replica Lag metric
140138
> Available only on replicas.
141139
142-
The **Read Replica Lag** metric shows the time since the last replayed transaction on a replica. If there are no transactions occurring on your primary, the metric reflects this time lag.
140+
The **Read Replica Lag** metric shows the time since the last replayed transaction on a replica. If there are no transactions occurring on your primary, the metric reflects this time lag. For instance if there are no transactions occurring on your primary server, and the last transaction was replayed 5 seconds ago, then the Read Replica Lag will show 5 second delay.
143141

144142
1. In the Azure portal, select read replica.
145143

0 commit comments

Comments
 (0)