Skip to content

Commit 60551ca

Browse files
authored
Merge pull request #295827 from MicrosoftDocs/main
3/6/2025 11:00 AM IST Publish
2 parents 6847e46 + b1daab1 commit 60551ca

File tree

56 files changed

+888
-322
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+888
-322
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: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to resolve data-loss problems with Azure Cache for Redis,
55

66

77
ms.topic: conceptual
8-
ms.date: 12/01/2021
8+
ms.date: 03/05/2025
99
---
1010

1111
# 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
2323
- [Redis instance failure](#redis-instance-failure)
2424

2525
> [!NOTE]
26-
> 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.
26+
> 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).
2727
>
2828
2929
## Partial loss of keys
@@ -58,8 +58,6 @@ expired_keys:46583
5858
db0:keys=3450,expires=2,avg_ttl=91861015336
5959
```
6060

61-
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.
62-
6361
### Key eviction
6462

6563
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/
7270
evicted_keys:13224
7371
```
7472

75-
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.
76-
7773
### Key deletion
7874

79-
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.
75+
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.
8076

8177
```azurecli-interactive
8278
# Commandstats
@@ -124,11 +120,9 @@ Caches in the Standard and Premium tiers offer much higher resiliency against da
124120

125121
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.
126122

127-
## Additional information
128-
129-
These articles provide more information on avoiding data loss:
123+
## Related content
130124

131125
- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
132126
- [Choosing the right tier](cache-overview.md#choosing-the-right-tier)
133127
- [Monitor Azure Cache for Redis](monitor-cache.md)
134-
- [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
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: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: azure-managed-redis
77
ms.custom:
88
- ignite-2024
99
ms.topic: conceptual
10-
ms.date: 11/15/2024
10+
ms.date: 03/05/2025
1111
---
1212

1313
# 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
2424
- [Redis instance failure](#redis-instance-failure)
2525

2626
> [!NOTE]
27-
> 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.
27+
> 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).
2828
>
2929
3030
## Partial loss of keys
@@ -59,7 +59,7 @@ expired_keys:46583
5959
db0:keys=3450,expires=2,avg_ttl=91861015336
6060
```
6161

62-
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.
62+
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.
6363

6464
### Key eviction
6565

@@ -73,8 +73,6 @@ You can monitor the number of evicted keys by using the [INFO](https://redis.io/
7373
evicted_keys:13224
7474
```
7575

76-
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.
77-
7876
### Key deletion
7977

8078
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
118116

119117
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.
120118

121-
## Additional information
122-
123-
These articles provide more information on avoiding data loss:
119+
## Related content
124120

125121
- [Troubleshoot Azure Managed Redis server-side issues](managed-redis-troubleshoot-server.md)
126122
- [Choosing the right tier](managed-redis-overview.md#choosing-the-right-tier)

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

articles/azure-functions/flex-consumption-plan.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,7 @@ Keep these other considerations in mind when using Flex Consumption plan:
142142
+ **Diagnostic settings**: Diagnostic settings aren't currently supported.
143143
+ **Certificates**: Loading certificates with the WEBSITE_LOAD_CERTIFICATES app setting, managed certificates, app service certificates, and other platform certificate-based features are currently not supported.
144144
+ **Key Vault References**: Key Vault references in app settings don't work when Key Vault is network access restricted, even if the function app has Virtual Network integration. The current workaround is to directly reference the Key Vault in code and read the required secrets.
145+
+ **Timezones**: `WEBSITE_TIME_ZONE` and `TZ` app settings are not currently supported when running on Flex Consumption plan.
145146

146147
## Related articles
147148

articles/backup/azure-file-share-support-matrix.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support Matrix for Azure files backup by using Azure Backup
33
description: Provides a summary of support settings and limitations when backing up Azure files.
44
ms.topic: reference
5-
ms.date: 02/27/2025
5+
ms.date: 03/06/2025
66
ms.custom: references_regions, engagement-fy24
77
ms.service: azure-backup
88
author: jyothisuri
@@ -128,7 +128,7 @@ Cross Subscription Backup (CSB) for Azure Files (preview) is currently available
128128
| Maximum number of files in a File Share | 10 million |
129129

130130
>[!Note]
131-
>If you have multiple backups scheduled per day, only the last scheduled backup of the day is transferred to the vault.
131+
>If you have multiple backups scheduled per day, only the last scheduled snapshot of the day is transferred to the vault.
132132
133133
---
134134

@@ -153,10 +153,7 @@ Cross Subscription Backup (CSB) for Azure Files (preview) is currently available
153153

154154
| Setting | Limit |
155155
| --- | --- |
156-
| Maximum size of a file | 1 TB |
157-
158-
>[!Note]
159-
>Restore to File Shares connected with Azure File sync service or with restricted network access isn't supported.
156+
| Maximum size of a file | 4 TB |
160157

161158
---
162159

articles/bastion/session-recording.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ The following sections outline considerations, limitations, and prerequisites fo
3333
* Azure Bastion is deployed to your virtual network. See [Tutorial - Deploy Bastion using specified settings](tutorial-create-host-portal.md) for steps.
3434
* Bastion must be configured to use **Premium SKU** for this feature. You can update to the Premium SKU from a lower SKU when you configure the session recording feature. To check your SKU and upgrade, if necessary, see [View or upgrade a SKU](upgrade-sku.md).
3535
* The virtual machine that you connect to must either be deployed to the virtual network that contains the bastion host, or to a virtual network that is directly peered to the Bastion virtual network.
36+
* To view/list the session recordings, user must have the **Storage Blob Data Reader** role.
3637

3738
## Enable session recording
3839

articles/container-apps/TOC.yml

Lines changed: 64 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -381,9 +381,27 @@
381381
- name: Turn on Java features
382382
href: java-feature-switch.md
383383
displayName: java
384+
- name: Automatic memory fitting (preview)
385+
href: java-memory-fit.md
386+
displayName: java
387+
- name: Build environment variables (preview)
388+
href: java-build-environment-variables.md
389+
displayName: java
384390
- name: Launch your first Java app
385-
href: java-get-started.md
386-
- name: Artificial Intelligence
391+
items:
392+
- name: Dockerfile
393+
href: /azure/developer/java/toolkit-for-intellij/java-get-started-dockerfile.md
394+
displayName: java
395+
- name: Github repository
396+
href: /azure/developer/java/toolkit-for-intellij/java-get-started-github-repository.md
397+
displayName: java
398+
- name: IntelliJ
399+
href: /azure/developer/java/toolkit-for-intellij/create-container-apps-intellij?toc=/azure/container-apps/toc.json&bc=/azure/container-apps/breadcrumb/toc.json
400+
displayName: java
401+
- name: Artifacts (preview)
402+
href: java-get-started.md
403+
displayName: java
404+
- name: Artificial intelligence
387405
items:
388406
- name: PetClinic AI
389407
items:
@@ -394,55 +412,51 @@
394412
href: java-petclinic-ai-tutorial.md
395413
displayName: java
396414
displayName: java
397-
- name: Launch your first Java microservice apps with managed Java components
398-
href: java-microservice-get-started.md
399-
displayName: java
400-
- name: Get started using IntelliJ
401-
href: /azure/developer/java/toolkit-for-intellij/create-container-apps-intellij?toc=/azure/container-apps/toc.json&bc=/azure/container-apps/breadcrumb/toc.json
402-
displayName: java
403-
- name: Automatic memory fitting (preview)
404-
href: java-memory-fit.md
405-
displayName: java
406-
- name: Build environment variables (preview)
407-
href: java-build-environment-variables.md
408-
displayName: java
409-
- name: Metrics
410-
href: java-metrics.md
411-
displayName: java
412-
- name: Scale with Java metrics
413-
href: java-metrics-scale-with-keda.md
414-
displayName: java
415-
- name: Connect to Eureka Server for Spring
416-
href: java-eureka-server.md
417-
displayName: java
418-
- name: Connect to Admin for Spring
419-
href: java-admin.md
420-
displayName: java
421-
- name: Connect to Config Server for Spring
422-
href: java-config-server.md
423-
displayName: java
424-
- name: Connect to Gateway for Spring
425-
href: java-gateway-for-spring.md
426-
displayName: java
427-
- name: Set dynamic logger level
428-
href: java-dynamic-log-level.md
429-
displayName: java
430-
- name: Tutorials
415+
- name: Java components
431416
items:
432-
- name: Integrate Eureka Server with Admin for Spring
433-
href: java-admin-eureka-integration.md
434-
displayName: java
435-
- name: Query managed component logs
436-
href: java-component-logs.md
437-
displayName: java
438-
- name: Configure Application Performance Management (APM) Java agent with init-container
439-
href: java-application-performance-management-config.md
440-
- name: Create a highly available Eureka server component cluster
441-
href: java-eureka-server-highly-available.md
442-
displayName: java
443-
- name: Build a Java metrics dashboard with Azure Managed Grafana
444-
href: java-metrics-with-grafana.md
445-
displayName: java
417+
- name: Launch your first Java microservice apps with managed Java components
418+
href: java-microservice-get-started.md
419+
displayName: java
420+
- name: Connect to Eureka Server for Spring
421+
href: java-eureka-server.md
422+
displayName: java
423+
- name: Integrate Eureka Server with Admin for Spring
424+
href: java-admin-eureka-integration.md
425+
displayName: java
426+
- name: Create a highly available Eureka server component cluster
427+
href: java-eureka-server-highly-available.md
428+
displayName: java
429+
- name: Connect to Admin for Spring
430+
href: java-admin.md
431+
displayName: java
432+
- name: Connect to Config Server for Spring
433+
href: java-config-server.md
434+
displayName: java
435+
- name: Connect to Gateway for Spring
436+
href: java-gateway-for-spring.md
437+
displayName: java
438+
- name: Monitoring
439+
items:
440+
- name: Java metrics
441+
href: java-metrics.md
442+
displayName: java
443+
- name: Query managed component logs
444+
href: java-component-logs.md
445+
displayName: java
446+
- name: Configure application performance management (APM) Java agent with init-container
447+
href: java-application-performance-management-config.md
448+
displayName: java
449+
- name: Scale with Java metrics
450+
href: java-metrics-scale-with-keda.md
451+
displayName: java
452+
- name: Build a Java metrics dashboard with Azure Managed Grafana
453+
href: java-metrics-with-grafana.md
454+
displayName: java
455+
- name: Diagnostic
456+
items:
457+
- name: Set dynamic logger level
458+
href: java-dynamic-log-level.md
459+
displayName: java
446460
- name: JavaScript
447461
items:
448462
- name: Overview

0 commit comments

Comments
 (0)