Skip to content

Commit 4744bad

Browse files
Merge pull request #255963 from haochenghuang/haochuang/feat-add-planned-maintenance
[ASA] Add how to configure planned maintenance
2 parents c48950f + 7c2c455 commit 4744bad

File tree

6 files changed

+97
-0
lines changed

6 files changed

+97
-0
lines changed
Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
---
2+
title: How to configure planned maintenance for Azure Spring Apps
3+
description: Describes how to configure planned maintenance for Azure Spring Apps.
4+
author: KarlErickson
5+
ms.author: haochuang
6+
ms.service: spring-apps
7+
ms.topic: how-to
8+
ms.date: 11/07/2023
9+
ms.custom:
10+
---
11+
12+
# How to configure planned maintenance
13+
14+
> [!NOTE]
15+
> Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
16+
17+
**This article applies to:** ❌ Standard consumption and dedicated (Preview) ✔️ Basic/Standard ✔️ Enterprise
18+
19+
This article describes how to configure planned maintenance in Azure Spring Apps.
20+
21+
Routine maintenance is necessary to keep the Azure Spring Apps platform up-to-date and secure. The maintenance, also called auto patching, includes security updates, bug fixes, new features, or performance improvements. Auto patching can be performed on components managed by Azure Spring Apps to support your Java applications, including JDK, APM, base OS image, managed middleware, and runtime infrastructure. For the maintenance to take effect, your applications restart within the maintenance window you specify, but the service quality and uptime guarantees continue to apply during this time.
22+
23+
## Configure maintenance for Azure Spring Apps
24+
25+
### [Azure portal](#tab/Azure-portal)
26+
27+
Use the following steps to configure planned maintenance in Azure Spring Apps:
28+
29+
1. Go to the service **Overview** page and select **Planned Maintenance**.
30+
31+
:::image type="content" source="media/how-to-configure-planned-maintenance/maintenance-section.png" alt-text="Screenshot of Azure portal that shows the Azure Spring Apps sidebar with Planned Maintenance highlighted.":::
32+
33+
1. Select **Choose your preferred time** to specify detailed configuration for the maintenance window.
34+
35+
:::image type="content" source="media/how-to-configure-planned-maintenance/maintenance-checkbox.png" alt-text="Screenshot of the Azure portal that shows the Planned maintenance page with the Choose your preferred time checkbox highlighted.":::
36+
37+
1. Select **Day of the week** to schedule the maintenance.
38+
39+
:::image type="content" source="media/how-to-configure-planned-maintenance/maintenance-week.png" alt-text="Screenshot of Azure portal that shows the Planned maintenance page with the Day of week option highlighted.":::
40+
41+
1. Select **Start time of upgrade**.
42+
43+
:::image type="content" source="media/how-to-configure-planned-maintenance/maintenance-time.png" alt-text="Screenshot of Azure portal that shows the Planned maintenance page with the Start time of upgrade option highlighted.":::
44+
45+
1. Select **Apply** to submit your configuration for planned maintenance.
46+
47+
### [Azure CLI](#tab/azure-cli)
48+
49+
Use the following command to configure planned maintenance:
50+
51+
```azurecli
52+
az spring update \
53+
--resource-group <resource-group-name> \
54+
--name <Azure-Spring-Apps-instance-name> \
55+
--enable-planned-maintenance \
56+
--planned-maintenance-day $DAY_OF_WEEK \
57+
--planned-maintenance-start-hour $START_HOUR
58+
```
59+
60+
---
61+
62+
Updating the configuration can take a few minutes. You get a notification when the configuration is complete.
63+
64+
> [!NOTE]
65+
> If you don't configure planned maintenance, the maintenance takes place at a time chosen by the service team, with the best effort to minimize business risks for most customers.
66+
67+
## Manage maintenance notification
68+
69+
Notifications and messages are sent out before and during the maintenance. The following table describes the message types and time details:
70+
71+
| Sequence number | Message type | Channel | Time the message is sent out |
72+
|-----------------|-----------------------------|---------------------|-----------------------------------------------------------|
73+
| 1 | Release note | Activity Log | At the end of the release rollout. |
74+
| 2 | Maintenance announcement | Planned Maintenance | Two weeks before the first available maintenance window. |
75+
| 3 | Start of maintenance window | Activity Log | At the start of the execution of the entire maintenance. |
76+
| 4 | Changelog of components | Activity Log | At the end of upgrade for each managed component. |
77+
| 5 | End of maintenance window | Activity Log | At the end of the execution of the entire maintenance. |
78+
| 6 | Feature update | What's New article | After the new feature becomes available to the customers. |
79+
80+
## Manage maintenance frequency
81+
82+
Currently, Azure Spring Apps performs one regular planned maintenance to upgrade the underlying infrastructure every three months. For a detailed maintenance timeline, check the notifications on the [Azure Service Health](https://azure.microsoft.com/get-started/azure-portal/service-health) page.
83+
84+
## Best practices
85+
86+
- When you configure planned maintenance for multiple service instances in the same region, the maintenance takes place within the same week. For example, if maintenance for cluster A is set on Monday and cluster B on Sunday, then cluster A is maintained before cluster B, in the same week.
87+
- If you have two service instances that span across [Azure paired regions](../availability-zones/cross-region-replication-azure.md#azure-paired-regions), the maintenance takes place in different weeks for such service instances, but there's no guarantee which region is maintained first. Follow each maintenance announcement for the exact information.
88+
- The length of the time window for the planned maintenance is fixed to 8 hours. For example, if the start time is set to 10:00, then the maintenance job is executed at any time between 10:00 and 18:00. The service team tries its best to finish the maintenance within this time window, but sometimes it might take longer.
89+
- You can't exempt a maintenance job regardless of how or whether planned maintenance is configured. If you have special requests for a maintenance time that can't be met with this feature, open a support ticket.
90+
91+
## Next steps
92+
93+
- [Analyze logs and metrics with diagnostics settings](./diagnostic-services.md)
111 KB
Loading
54.3 KB
Loading
143 KB
Loading
115 KB
Loading

articles/spring-apps/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -203,6 +203,8 @@ items:
203203
href: how-to-outbound-public-ip.md
204204
- name: Move across regions
205205
href: how-to-move-across-regions.md
206+
- name: Configure planned maintenance
207+
href: how-to-configure-planned-maintenance.md
206208
- name: Scale
207209
items:
208210
- name: Manually scale an app
@@ -415,6 +417,8 @@ items:
415417
href: how-to-outbound-public-ip.md
416418
- name: Move across regions
417419
href: how-to-move-across-regions.md
420+
- name: Configure planned maintenance
421+
href: how-to-configure-planned-maintenance.md
418422
- name: Scale
419423
items:
420424
- name: Manually scale an app

0 commit comments

Comments
 (0)