PolarDB:View and manage scheduled events

Event urgency levels

Scheduled events fall into two urgency levels:

• [S0: Urgent] Risk fixing: Unexpected events that must be addressed quickly to prevent faults—for example, emergency hardware replacement, faulty version upgrades, host exception fixes, and SSL certificate renewals before expiration. Notifications may arrive three or more days in advance, but the rescheduling window is short.

• [S1: Scheduled] System maintenance: Low-risk issues or planned software and hardware upgrades. Notifications arrive more than three days in advance, and you can cancel these events.

Set up notifications

PolarDB sends notifications 1–3 days before an event, based on urgency.

To receive notifications, configure contacts in Message Center for ApsaraDB Fault or Maintenance Notifications. Add database operations and maintenance (O&M) personnel as contacts. Select Email as the notification method for the highest delivery reliability. Internal Messages is also available.

Figure 1 Entry for Message Settings in the Message Center console

Figure 2 Notification settings for ApsaraDB Fault or Maintenance NotificationsMessage CenterThe notification methods include Email and Internal Messages. We recommend that you select Email to improve the success rate of notifications.

For event-driven O&M automation, subscribe to CloudMonitor system events. CloudMonitor pushes lifecycle notifications—subscription, start, end, and cancellation—for each maintenance event. For setup instructions, see Manage event subscription policies (recommended). For information about CloudMonitor system events to which you can subscribe, see the "Appendix 1 CloudMonitor-related system events" section of this topic.

Sample CloudMonitor event payload:

{
  "eventId": "c864b30b-7f69-5f04-b0e7-8dfb0eabcfd9",
  "product": "RDS",
  "reason": "Host software/hardware upgrade",
  "extra": {
    "impactEn": "Transient instance disconnection",
    "eventCode": "rds_apsaradb_transfer",
    "eventNameEn": "Instance migration",
    "switchTime": "2024-09-15T01:30:00+08:00",
    "startTime": "2024-09-14T21:30:00+08:00",
    "cancelCode": "OutOfGoodPerfBySoftHardwareUpgrade",
    "detailCode": "HostSoftHardwareUpgrade",
    "instanceInfo": ""
  },
  "instanceId": "rm-2ze9d66o65q1g02g6",
  "eventType": "Maintenance",
  "instanceComment": "rm-2ze9d66o65q1g02g6",
  "instanceType": "Instance",
  "publishTime": "2024-09-10T16:01:47+08:00"
}

Key fields in the payload:

View scheduled events

1. Log on to the PolarDB console.

2. In the left-side navigation pane, choose Event Center (formerly known as Event Management) > Scheduled Events. In the top navigation bar, select the region where your cluster resides.

3. On the Scheduled Events page, view event details. By default, events in the Planned state are displayed. Click the Completed or Canceled tab to view historical events.

   Attribute	Example	Description
   Event type	Risk fixing	The urgency level: risk fixing or system maintenance.
   Status	Pending	The scheduling status. See Event statuses below.
   Event type	Minor version update	The specific type of maintenance event. For a full list, see Event types and impacts.
   Cause	-	The cause of the event.
   Business impact	Transient connections	How the event affects your workloads. Varies by event type.
   O&M suggestions	Make sure that your applications are automatically configured to reconnect to your cluster.	Recommended actions before or during the event.
   Start time	-	When the event enters the scheduling queue. Empty if the status is Waiting Setting Time. Before this time, the cluster is not affected. After this time, cluster-level operations (such as changing configurations or cross-zone migrations) are temporarily unavailable.
   Scheduled switchover time	-	The estimated time when a transient connection occurs due to a primary/secondary or link switchover. In extreme cases, up to two switchovers may occur.
   Deadline	-	The latest time by which you can configure the execution time. The switchover time you set cannot be later than this deadline.
   Cancelable	Yes	Whether you can cancel this event. Available for most system O&M events.
   Schedule changeable	Yes	Whether you can reschedule this event. Not available for urgent risk fixing events with a short window.

Reschedule an event

Select the events you want to reschedule and click Schedule Event. Choose one of the following options:

• Immediate execution: Starts the event immediately. The current time is used as the start time, and the event enters the execution queue right away.

• Switchover at a specified time: Select a switchover time within the allowed range. The start time is automatically calculated based on the switchover time you choose. The new start time cannot be earlier than the current time.

When you cannot reschedule an event:

Rescheduling is blocked if any of the following conditions apply:

• The event is in the Executing state.

• The event's start time has already passed.

• The current time is later than the event's deadline.

• The new start time of the event is earlier than the current time.

• The switchover time for this event cannot be changed.

To set the switchover time beyond the deadline (when you accept the associated risks), submit a ticket.

Set a recurring maintenance window

A recurring time window lets you define a preferred schedule for future maintenance events. When a new event is created, the system uses this window to calculate its execution time instead of deriving it from your cluster's maintenance window.

Click Recurring Time Window Settings in the upper-right corner of the event list. You can set the window by month or week.

Example: If you set the recurring window to 02:00–03:00 on Mondays and Tuesdays, and a new event's allowed time range spans this Tuesday through next Sunday, the eligible switchover slots are Tuesday 02:00–03:00 and next Monday 02:00–03:00. The system preferentially schedules the switchover on Tuesday.

For information about setting the maintenance window for individual clusters, see Set a maintenance window.

Event types and impacts

FAQ

API reference