Skip to content

Commit aa09fe6

Browse files
committed
Remove external links
1 parent 9192c8e commit aa09fe6

File tree

5 files changed

+3
-13
lines changed

5 files changed

+3
-13
lines changed

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

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,3 @@ The [Access Azure Cache for Redis Monitoring data](https://github.com/rustd/Redi
6969
## An X-style clone written using PHP and Redis
7070

7171
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.
72-
73-
## Bandwidth monitor
74-
75-
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.

articles/azure-cache-for-redis/cache-troubleshoot-data-loss.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,5 +125,4 @@ Consider using [Redis data persistence](https://redis.io/topics/persistence) and
125125
- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
126126
- [Choosing the right tier](cache-overview.md#choosing-the-right-tier)
127127
- [Monitor Azure Cache for Redis](monitor-cache.md)
128-
- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
129-
- [Sample code for examining keyspace notifications](https://gist.github.com/JonCole/0d6205b4771e5c803bc1e085517484a2#file-rediskeyspacenotificationsexample-cs)
128+
- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)

articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Here's the client-side troubleshooting.
4444

4545
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.
4646

47-
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:
47+
You can use `TimeoutException` messages from StackExchange.Redis to further investigate:
4848

4949
```output
5050
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:
8989

9090
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.
9191

92-
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).
93-
9492
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).
9593

9694
### TCP settings for Linux based client applications

articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-data-loss.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,4 +122,3 @@ Consider using [Redis data persistence](https://redis.io/topics/persistence) and
122122
- [Choosing the right tier](managed-redis-overview.md#choosing-the-right-tier)
123123
- [Monitor Azure Managed Redis](../monitor-cache.md)
124124
- [How can I run Redis commands?](managed-redis-development-faq.yml#how-can-i-run-redis-commands-)
125-
- [Sample code for examining keyspace notifications](https://gist.github.com/JonCole/0d6205b4771e5c803bc1e085517484a2#file-rediskeyspacenotificationsexample-cs)

articles/azure-cache-for-redis/managed-redis/managed-redis-troubleshoot-timeouts.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Here's the client-side troubleshooting.
4343

4444
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.
4545

46-
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:
46+
You can use `TimeoutException` messages from StackExchange.Redis to further investigate:
4747

4848
```output
4949
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:
8888

8989
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.
9090

91-
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).
92-
9391
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).
9492

9593
### TCP settings for Linux based client applications

0 commit comments

Comments
 (0)