Skip to content

Commit ae02e02

Browse files
committed
Removed comments, changed date
1 parent d26885d commit ae02e02

File tree

2 files changed

+3
-6
lines changed

2 files changed

+3
-6
lines changed

articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: flang-msft
55

66
ms.service: cache
77
ms.topic: conceptual
8-
ms.date: 03/28/2023
8+
ms.date: 03/23/2023
99
ms.author: franlanglois
1010

1111
---
@@ -25,7 +25,7 @@ Active geo-replication groups up to five instances of Enterprise Azure Cache for
2525
|--------- |:------------------:|:----------:|:---------:|
2626
|Available | No | No | Yes |
2727

28-
<!-- What do you think of this table? -->
28+
2929
|Tier | Available|
3030
|:---|:---:|
3131
|Basic, Standard | No |
@@ -146,7 +146,6 @@ As before, you need to list both _Cache1_ and _Cache2_ using the `-LinkedDatabas
146146
Due to the potential for inadvertent data loss, you can't use the `FLUSHALL` and `FLUSHDB` Redis commands with any cache instance residing in a geo-replication group. Instead, use the **Flush Cache(s)** button located at the top of the **Active geo-replication** working pane.
147147

148148
:::image type="content" source="media/cache-how-to-active-geo-replication/cache-active-flush.png" alt-text="Screenshot showing Active geo-replication selected in the Resource menu and the Flush cache feature has a red box around it.":::
149-
<!-- **FRAN--need a screenshot picture here** -->
150149

151150
> [!IMPORTANT]
152151
> Be careful when using the **Flush Caches** feature. Selecting the button removes all data from the current cache and from ALL linked caches in the geo-replication group.

articles/azure-cache-for-redis/cache-monitor-diagnostic-settings.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: flang-msft
66
ms.author: franlanglois
77
ms.service: cache
88
ms.topic: how-to
9-
ms.date: 03/28/2023
9+
ms.date: 03/23/2023
1010
ms.custom: template-how-to, devx-track-azurecli
1111
ms.devlang: azurecli
1212
---
@@ -110,15 +110,13 @@ For more pricing information, [Azure Monitor pricing](https://azure.microsoft.co
110110

111111
1. Navigate to your Azure Cache for Redis account. Open the **Diagnostic Settings - Auditing** pane under the **Monitoring** section on the left. Then, select **Add diagnostic setting**.
112112
:::image type="content" source="media/cache-monitor-diagnostic-settings/cache-enterprise-auditing.png" alt-text="Screenshot of Diagnostic settings - Auditing selected in the Resource menu.":::
113-
<!-- **FRAN--need a new picture here** -->
114113

115114
1. In the **Diagnostic Setting - Auditing** pane, select **Connection events** from **Categories**.
116115

117116
For more detail on the data logged, see below [Contents of the Connection Logs](#contents-of-the-connection-logs).
118117

119118
1. Once you select **Connection events**, send your logs to your preferred destination. Select the information in the working pane.
120119
:::image type="content" source="media/cache-monitor-diagnostic-settings/cache-enterprise-connection-events.png" alt-text="Screenshot showing Connection events being checked in working pane.":::
121-
<!-- **FRAN--need a new picture here** -->
122120

123121

124122
---

0 commit comments

Comments
 (0)