Merge pull request #280779 from cdpark/horz-monitor-redis

Q&M: Curate 27 SOX Azure Monitor horizontals articles to reduce duplication -- Redis cache

Author: denrea

articles/azure-cache-for-redis/.openpublishing.redirection.redis-cache.json

@@ -230,6 +230,11 @@
             "redirect_url": "/azure/azure-cache-for-redis/",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-cache-for-redis/cache-how-to-monitor.md",
+            "redirect_url": "/azure/azure-cache-for-redis/monitor-cache",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/redis-cache/scripts/cache-keys-ports.md",
             "redirect_url": "/azure/azure-cache-for-redis/scripts/create-manage-cache",

articles/azure-cache-for-redis/TOC.yml

@@ -108,14 +108,14 @@
 
 - name: Logs and monitoring
   items:
-  - name: Monitor
+  - name: Monitor Cache for Redis
     href: monitor-cache.md
-  - name: Monitor Azure Cache for Redis
-    href: cache-how-to-monitor.md
-  - name: Use insights to understand performance and utilization
+  - name: Monitor using insights
     href: cache-insights-overview.md
-  - name: Monitor with diagnostic logs
+  - name: Monitor using diagnostic settings
     href: cache-monitor-diagnostic-settings.md
+  - name: List of Redis metrics
+    href: monitor-cache-reference.md#metrics
 - name: Scaling and performance
   items:
   - name: Change the size and tier of a cache

articles/azure-cache-for-redis/cache-best-practices-memory-management.md

@@ -38,7 +38,7 @@ Configure your [maxmemory-reserved setting](cache-configure.md#memory-policies)
 
 - The `maxfragmentationmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, that is reserved to accommodate for memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high. When memory is reserved for such operations, it's unavailable for storage of cached data. The allowed range for `maxfragmentationmemory-reserved` is 10% - 60% of `maxmemory`. If you try to set these values lower than 10% or higher than 60%, they are re-evaluated and set to the 10% minimum and 60% maximum. The values are rendered in megabytes.
 
-- One thing to consider when choosing a new memory reservation value (`maxmemory-reserved` or `maxfragmentationmemory-reserved`) is how this change might affect a cache with large amounts of data in it that is already running. For instance, if you have a 53-GB cache with 49 GB of data and then change the reservation value to 8 GB, the max available memory for the system will drop to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system must evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](cache-how-to-monitor.md#create-your-own-metrics).
+- One thing to consider when choosing a new memory reservation value (`maxmemory-reserved` or `maxfragmentationmemory-reserved`) is how this change might affect a cache with large amounts of data in it that is already running. For instance, if you have a 53-GB cache with 49 GB of data and then change the reservation value to 8 GB, the max available memory for the system will drop to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system must evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](monitor-cache.md#create-your-own-metrics).
 
 > [!NOTE]
 > When you scale a cache up or down, both `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings automatically scale in proportion to the cache size. For example, if `maxmemory-reserved` is set to 3 GB on a 6-GB cache, and you scale to 12-GB cache, the settings automatically get updated to 6 GB during scaling. When you scale down, the reverse happens.

articles/azure-cache-for-redis/cache-configure.md

@@ -205,7 +205,7 @@ The **maxmemory-reserved** setting configures the amount of memory in MB per ins
 
 The **maxfragmentationmemory-reserved** setting configures the amount of memory in MB per instance in a cluster that is reserved to accommodate for memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high. When memory is reserved for such operations, it's unavailable for storage of cached data. The minimum and maximum values on the slider are 10% and 60%, shown in megabytes. You must set the value in that range.
 
-When choosing a new memory reservation value (**maxmemory-reserved** or **maxfragmentationmemory-reserved**), consider how this change might affect a cache that is already running with large amounts of data in it. For instance, if you have a 53-GB cache with 49 GB of data, then change the reservation value to 8 GB, this change drops the max available memory for the system down to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system has to evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](cache-how-to-monitor.md#create-your-own-metrics).
+When choosing a new memory reservation value (**maxmemory-reserved** or **maxfragmentationmemory-reserved**), consider how this change might affect a cache that is already running with large amounts of data in it. For instance, if you have a 53-GB cache with 49 GB of data, then change the reservation value to 8 GB, this change drops the max available memory for the system down to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system has to evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](monitor-cache.md#create-your-own-metrics).
 
 > [!IMPORTANT]
 > The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available for Basic,Standard and Premium caches.
@@ -361,7 +361,7 @@ To reboot one or more nodes of your cache, select the desired nodes and select *
 The **Monitoring** section allows you to configure diagnostics and monitoring for your Azure Cache for Redis instance.
 
 - For more information on Azure Cache for Redis monitoring and diagnostics, see [Monitor Azure Cache for Redis](monitor-cache.md).
-- For information on how to set up and use Azure Cache for Redis monitoring and diagnostics, see [How to monitor Azure Cache for Redis](cache-how-to-monitor.md).
+- For information on how to set up and use Azure Cache for Redis monitoring and diagnostics, see [Monitor Azure Cache for Redis](monitor-cache.md).
 
 :::image type="content" source="media/cache-configure/redis-cache-diagnostics.png" alt-text="Diagnostics":::
 
@@ -371,11 +371,11 @@ Use **Insights** to see groups of predefined tiles and charts to use as starting
 
 ### Metrics
 
-Select **Metrics** to create your own custom chart to track the metrics you want to see for your cache. For more information, see [Create your own metrics](cache-how-to-monitor.md#create-your-own-metrics).
+Select **Metrics** to create your own custom chart to track the metrics you want to see for your cache. For more information, see [Create your own metrics](monitor-cache.md#create-your-own-metrics).
 
 ### Alerts
 
-Select **Alerts** to configure alerts based on Azure Cache for Redis metrics. For more information, see [Create alerts](cache-how-to-monitor.md#create-alerts).
+Select **Alerts** to configure alerts based on Azure Cache for Redis metrics. For more information, see [Create alerts](monitor-cache.md#create-alerts).
 
 ### Diagnostic settings
 
@@ -398,13 +398,13 @@ Further information can be found on the **Recommendations** in the working pane
 
 :::image type="content" source="media/cache-configure/redis-cache-recommendations.png" alt-text="Screenshot that shows Advisor recommendations":::
 
-You can monitor these metrics on the [Monitoring](cache-how-to-monitor.md) section of the Resource menu.
+You can monitor these metrics on the [Monitoring](monitor-cache.md) section of the Resource menu.
 
 | Azure Cache for Redis metric | More information |
 | --- | --- |
 | Network bandwidth usage |[Cache performance - available bandwidth](./cache-planning-faq.yml#azure-cache-for-redis-performance) |
 | Connected clients |[Default Redis server configuration - max clients](#maxclients) |
-| Server load |[Redis Server Load](cache-how-to-monitor.md#view-cache-metrics) |
+| Server load |[Redis Server Load](monitor-cache.md#view-cache-metrics) |
 | Memory usage |[Cache performance - size](./cache-planning-faq.yml#azure-cache-for-redis-performance) |
 
 To upgrade your cache, select **Upgrade now** to change the pricing tier and [scale](#scale) your cache. For more information on choosing a pricing tier, see [Choosing the right tier](cache-overview.md#choosing-the-right-tier).
@@ -551,4 +551,4 @@ For more information about Redis commands, see [https://redis.io/commands](https
 ## Related content
 
 - [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
-- [Monitor Azure Cache for Redis](cache-how-to-monitor.md)
+- [Monitor Azure Cache for Redis](monitor-cache.md)

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

@@ -200,15 +200,15 @@ When the failover process is initiated, you see the link provisioning status upd
 
 ### Can I track the health of the geo-replication link?
 
-Yes, there are several [metrics available](cache-how-to-monitor.md#list-of-metrics) to help track the status of the geo-replication. These metrics are available in the Azure portal.
+Yes, there are several [metrics available](monitor-cache-reference.md#metrics) to help track the status of the geo-replication. These metrics are available in the Azure portal.
 
 - **Geo Replication Healthy** shows the status of the geo-replication link. The link show as unhealthy if either the geo-primary or geo-secondary caches are down. This is typically due to standard patching operations, but it could also indicate a failure situation.
 - **Geo Replication Connectivity Lag** shows the time since the last successful data synchronization between geo-primary and geo-secondary.
 - **Geo Replication Data Sync Offset** shows the amount of data that has yet to be synchronized to the geo-secondary cache.
 - **Geo Replication Fully Sync Event Started** indicates that a full synchronization action has been initiated between the geo-primary and geo-secondary caches. This occurs if standard replication can't keep up with the number of new writes.
 - **Geo Replication Full Sync Event Finished** indicates that a full synchronization action was completed.
 
-There's also a [prebuilt workbook](cache-how-to-monitor.md#organize-with-workbooks) called the **Geo-Replication Dashboard** that includes all of the geo-replication health metrics in one view. Using this view is recommended because it aggregates information that is emitted only from the geo-primary or geo-secondary cache instances.
+There's also a [prebuilt workbook](cache-insights-overview.md#workbooks) called the **Geo-Replication Dashboard** that includes all of the geo-replication health metrics in one view. Using this view is recommended because it aggregates information that is emitted only from the geo-primary or geo-secondary cache instances.
 
 ### Can I link more than two caches together?
 
@@ -228,7 +228,7 @@ Yes, as long as both caches have the same number of shards.
 
 ### Can I use geo-replication with my caches in a VNet?
 
-We recommend using using Azure Private Link over VNet injection in most cases. For more information see, [Migrate from VNet injection caches to Private Link caches](cache-vnet-migration.md).
+We recommend using Azure Private Link over VNet injection in most cases. For more information see, [Migrate from VNet injection caches to Private Link caches](cache-vnet-migration.md).
 
 While it is still technically possible to use VNet injection when geo-replicating your caches, we recommend Azure Private Link.