Help Center/ TaurusDB/ User Guide/ Event Management
Updated on 2026-08-13 GMT+08:00
View PDF
Share

Event Management

Scenarios

To ensure stable TaurusDB operations, the system periodically checks the database version and underlying software and hardware status of each instance. When risks that cannot be automatically resolved are detected, the system generates and reports events, which may affect workload continuity.

You can view the instance ID, event type, event cause, event status, and service impact on the console and also manually adjust the event execution time to minimize the impact.

Event Types

Table 1 Supported events

Event Type

Risk Level

Event Cause

Minor version upgrade

Major

The risky version needs to be upgraded.

Read replica rebuild

Major

Underlying software or hardware faults require rebuilding read replicas to avoid further failures.

High CPU or memory load

Major

An instance's CPU or memory usage has reached the threshold and the instance specifications need to be changed.

Required Permissions

  • If you authorize the execution of a high CPU usage event using an account, no additional configuration is required. If you authorize the execution of a high CPU usage event as an IAM user for the first time, the IAM user must be granted the permission to create agencies.
  • To authorize the execution of high CPU or memory usage events, the following IAM permissions are required:
    Table 2 IAM permissions and agencies

    IAM Policy

    Permission

    Agency

    Role/Policy-based
    • iam:agencies:listAgencies
    • iam:agencies:createAgency
    • iam:permissions:listRolesForAgencyOnProject
    • iam:permissions:grantRoleToGroupOnProject
    • iam:permissions:grantRoleToAgencyOnProject
    • iam:roles:listRoles
    • iam:roles:createRole

    If you do not have these permissions, create a custom policy.

    The system will automatically create the RDSAccessProjectResource agency. This agency is visible to you. Deleting the agency will result in auto scaling failures.

    Identity policy-based
    • iam:agencies:listAgencies
    • iam:agencies:createServiceLinkedAgencyV5

    If you do not have these permissions, create a custom identity policy.

    The system will automatically create the ServiceLinkedAgencyForGaussDBforMySQL agency. This agency is visible to you but cannot be deleted.

Precautions

Executing certain events may cause a brief workload interruption. To help workloads recover quickly, ensure that your application can automatically reconnect to the DB instance.

Constraints

Procedure

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. In the navigation pane, choose Events to view event information.

    Figure 1 Events

    • Authorize: You must grant authorization for an event to be executed immediately or during a scheduled maintenance window. If an authorized event is in the Pending execution state, you can modify the scheduled maintenance window.
      Figure 2 Authorize Event Execution

    • Cancel: For non-critical events, you can cancel them manually. Canceled events will still appear in the event list but cannot be filtered using the filter bar.
    • Modify Execution Time: Change the planned execution time of an event.
      Figure 3 Modifying the event execution time

    • Event Execution Entity: View the object (instance ID or node ID) on which the event is executed and the execution status.