Merge pull request #295816 from flang-msft/fxl---remove-links-to-gists

JillGrant615 · web-flow · commit 5e139e074114 · 2025-03-05T21:25:09.000-07:00
Fxl---remove links to gists
diff --git a/articles/azure-cache-for-redis/cache-redis-samples.md b/articles/azure-cache-for-redis/cache-redis-samples.md
@@ -69,7 +69,3 @@ The [Access Azure Cache for Redis Monitoring data](https://github.com/rustd/Redi
 ## An X-style clone written using PHP and Redis
 
 The [Retwis](https://github.com/SyntaxC4-MSFT/retwis) sample is the Redis Hello World. It's a minimal X-style social network clone written using Redis and PHP using the [Predis](https://github.com/nrk/predis) client. The source code is designed to be simple and at the same time to show different Redis data structures.
-
-## Bandwidth monitor
-
-The [Bandwidth monitor](https://github.com/JonCole/SampleCode/tree/master/BandWidthMonitor) sample allows you to monitor the bandwidth used on the client. To measure the bandwidth, run the sample on the cache client machine, make calls to the cache, and observe the bandwidth reported by the bandwidth monitor sample.
diff --git a/articles/azure-cache-for-redis/cache-troubleshoot-data-loss.md b/articles/azure-cache-for-redis/cache-troubleshoot-data-loss.md
@@ -5,7 +5,7 @@ description: Learn how to resolve data-loss problems with Azure Cache for Redis,
 
 
 ms.topic: conceptual
-ms.date: 12/01/2021
+ms.date: 03/05/2025
 ---
 
 # Troubleshoot data loss in Azure Cache for Redis
@@ -23,7 +23,7 @@ This article discusses how to diagnose actual or perceived data losses that migh
   - [Redis instance failure](#redis-instance-failure)
 
 > [!NOTE]
-> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Additional information](#additional-information) section.
+> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Related Content](#related-content).
 >
 
 ## Partial loss of keys
@@ -58,8 +58,6 @@ expired_keys:46583
 db0:keys=3450,expires=2,avg_ttl=91861015336
 ```
 
-You can also look at diagnostic metrics for your cache, to see if there's a correlation between when the key went missing and a spike in expired keys. See the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix) for information about using `keyspace` notifications or `MONITOR`  to debug these types of issues.
-
 ### Key eviction
 
 Azure Cache for Redis requires memory space to store data. It purges keys to free up available memory when necessary. When the **used_memory** or **used_memory_rss** values in the [INFO](https://redis.io/commands/info) command approach the configured **maxmemory** setting, Azure Cache for Redis starts evicting keys from memory based on [cache policy](https://redis.io/topics/lru-cache).
@@ -72,11 +70,9 @@ You can monitor the number of evicted keys by using the [INFO](https://redis.io/
 evicted_keys:13224
 ```
 
-You can also look at diagnostic metrics for your cache, to see if there's a correlation between when the key went missing and a spike in evicted keys. See the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix) for information about using keyspace notifications or **MONITOR** to debug these types of issues.
-
 ### Key deletion
 
-Redis clients can issue the [DEL](https://redis.io/commands/del) or [HDEL](https://redis.io/commands/hdel) command to explicitly remove keys from Azure Cache for Redis. You can track the number of delete operations by using the [INFO](https://redis.io/commands/info) command. If **DEL** or **HDEL** commands have been called, they'll be listed in the `Commandstats` section.
+Redis clients can issue the [DEL](https://redis.io/commands/del) or [HDEL](https://redis.io/commands/hdel) command to explicitly remove keys from Azure Cache for Redis. You can track the number of delete operations by using the [INFO](https://redis.io/commands/info) command. If **DEL** or **HDEL** commands have been called, they are listed in the `Commandstats` section.
 
 ```azurecli-interactive
 # Commandstats
@@ -124,11 +120,9 @@ Caches in the Standard and Premium tiers offer much higher resiliency against da
 
 Consider using [Redis data persistence](https://redis.io/topics/persistence) and [geo-replication](./cache-how-to-geo-replication.md) to improve protection of your data against these infrastructure failures.
 
-## Additional information
-
-These articles provide more information on avoiding data loss:
+## Related content
 
 - [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
 - [Choosing the right tier](cache-overview.md#choosing-the-right-tier)
 - [Monitor Azure Cache for Redis](monitor-cache.md)
-- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
+- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
diff --git a/articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md b/articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md
@@ -44,7 +44,7 @@ Here's the client-side troubleshooting.
 
 Bursts of traffic combined with poor `ThreadPool` settings can result in delays in processing data already sent by the Redis server but not yet consumed on the client side. Check the metric "Errors" (Type: UnresponsiveClients) to validate if your client hosts can keep up with a sudden spike in traffic.
 
-Monitor how your `ThreadPool` statistics change over time using [an example `ThreadPoolLogger`](https://github.com/JonCole/SampleCode/blob/master/ThreadPoolMonitor/ThreadPoolLogger.cs). You can use  `TimeoutException` messages from StackExchange.Redis to further investigate:
+You can use  `TimeoutException` messages from StackExchange.Redis to further investigate:
 
 ```output
     System.TimeoutException: Timeout performing EVAL, inst: 8, mgr: Inactive, queue: 0, qu: 0, qs: 0, qc: 0, wr: 0, wq: 0, in: 64221, ar: 0,
@@ -89,8 +89,6 @@ To mitigate a client's high CPU usage:
 
 Depending on the architecture of client machines, they might have limitations on how much network bandwidth they have available. If the client exceeds the available bandwidth by overloading network capacity, then data isn't processed on the client side as quickly as the server is sending it. This situation can lead to timeouts.
 
-Monitor how your Bandwidth usage change over time using [an example `BandwidthLogger`](https://github.com/JonCole/SampleCode/blob/master/BandWidthMonitor/BandwidthLogger.cs). This code might not run successfully in some environments with restricted permissions (like Azure web sites).
-
 To mitigate, reduce network bandwidth consumption or increase the client VM size to one with more network capacity. For more information, see [Large request or response size](cache-best-practices-development.md#large-request-or-response-size).
 
 ### TCP settings for Linux based client applications
diff --git a/articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-data-loss.md b/articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-data-loss.md
@@ -7,7 +7,7 @@ ms.service: azure-managed-redis
 ms.custom:
   - ignite-2024
 ms.topic: conceptual
-ms.date: 11/15/2024
+ms.date: 03/05/2025
 ---
 
 # Troubleshoot data loss in Azure Managed Redis (preview)
@@ -24,7 +24,7 @@ This article discusses how to diagnose actual or perceived data losses that migh
   - [Redis instance failure](#redis-instance-failure)
 
 > [!NOTE]
-> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Additional information](#additional-information) section.
+> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Related content](#related-content).
 >
 
 ## Partial loss of keys
@@ -59,7 +59,7 @@ expired_keys:46583
 db0:keys=3450,expires=2,avg_ttl=91861015336
 ```
 
-You can also look at diagnostic metrics for your cache, to see if there's a correlation between when the key went missing and a spike in expired keys. See the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix) for information about using `keyspace` notifications or `MONITOR`  to debug these types of issues.
+You can examine the diagnostic metrics for your cache to see if there's a correlation between when the key went missing and a spike in evicted keys.
 
 ### Key eviction
 
@@ -73,8 +73,6 @@ You can monitor the number of evicted keys by using the [INFO](https://redis.io/
 evicted_keys:13224
 ```
 
-You can also look at diagnostic metrics for your cache, to see if there's a correlation between when the key went missing and a spike in evicted keys. See the Appendix of [Debugging Redis Keyspace Misses](https://gist.github.com/JonCole/4a249477142be839b904f7426ccccf82#appendix) for information about using keyspace notifications or **MONITOR** to debug these types of issues.
-
 ### Key deletion
 
 Redis clients can issue the [DEL](https://redis.io/commands/del) or [HDEL](https://redis.io/commands/hdel) command to explicitly remove keys from Azure Managed Redis. You can track the number of delete operations by using the [INFO](https://redis.io/commands/info) command. If **DEL** or **HDEL** commands have been called, they'll be listed in the `Commandstats` section.
@@ -118,9 +116,7 @@ Redis is an in-memory data store. Data is kept on the physical or virtual machin
 
 Consider using [Redis data persistence](https://redis.io/topics/persistence) and [geo-replication](../cache-how-to-geo-replication.md) to improve protection of your data against these infrastructure failures.
 
-## Additional information
-
-These articles provide more information on avoiding data loss:
+## Related content
 
 - [Troubleshoot Azure Managed Redis server-side issues](managed-redis-troubleshoot-server.md)
 - [Choosing the right tier](managed-redis-overview.md#choosing-the-right-tier)
diff --git a/articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-timeouts.md b/articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-timeouts.md
@@ -43,7 +43,7 @@ Here's the client-side troubleshooting.
 
 Bursts of traffic combined with poor `ThreadPool` settings can result in delays in processing data already sent by the Redis server but not yet consumed on the client side. Check the metric "Errors" (Type: UnresponsiveClients) to validate if your client hosts can keep up with a sudden spike in traffic.
 
-Monitor how your `ThreadPool` statistics change over time using [an example `ThreadPoolLogger`](https://github.com/JonCole/SampleCode/blob/master/ThreadPoolMonitor/ThreadPoolLogger.cs). You can use  `TimeoutException` messages from StackExchange.Redis to further investigate:
+You can use  `TimeoutException` messages from StackExchange.Redis to further investigate:
 
 ```output
     System.TimeoutException: Timeout performing EVAL, inst: 8, mgr: Inactive, queue: 0, qu: 0, qs: 0, qc: 0, wr: 0, wq: 0, in: 64221, ar: 0,
@@ -88,8 +88,6 @@ To mitigate a client's high CPU usage:
 
 Depending on the architecture of client machines, they might have limitations on how much network bandwidth they have available. If the client exceeds the available bandwidth by overloading network capacity, then data isn't processed on the client side as quickly as the server is sending it. This situation can lead to timeouts.
 
-Monitor how your Bandwidth usage change over time using [an example `BandwidthLogger`](https://github.com/JonCole/SampleCode/blob/master/BandWidthMonitor/BandwidthLogger.cs). This code might not run successfully in some environments with restricted permissions (like Azure web sites).
-
 To mitigate, reduce network bandwidth consumption or increase the client VM size to one with more network capacity. For more information, see [Large request or response size](managed-redis-best-practices-development.md#large-request-or-response-size).
 
 ### TCP settings for Linux based client applications
