Monitoring and Alarm
Monitoring trend chart
On the "Monitor" page of the instance, you can see the database instance-level monitoring trend chart. You can view monitoring data from the last 14 days to the last hour.
The monitoring trend chart includes CPU occupancy rate, disk usage rate, memory usage rate, network interface card (NIC) traffic, number of requests, number of links, maximum transaction execution time, slow query, and master-slave delay information.
"CPU occupancy rate" monitoring item is taken as an example.
- Click the monitoring trend chart zoom button to view details.
- Select the statistical item, sampling cycle, and statistical time to view updated data.
Description of monitoring items
| Monitoring items | Description | Monitoring frequency | Monitoring cycle |
|---|---|---|---|
| CPU occupancy rate | CPC usage rate of the instance (excluding the occupancy by the operating system). | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| Data space: disk usage rate | Disk space for data/purchased disk space | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| System space: disk usage rate | Disk space for data plus disk space for log/purchased disk space | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| Means the memory usage rate | Percentage of memory for instance to total memory | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| NIC traffic | Including inflow traffic and outflow traffic. Unit Byte | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| number of requests | Including query request times, updating request times, and all SQL times, | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| number of connections | Including client links and active threads. | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| Maximum transaction execution time | Maximum SQL transaction execution time | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| Slow query | Number of slow queries by users | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
| Leader-follower delay | master-slave instance delay time, unit: s | Frequency: 60s/time, cycle: 1 hour, 6 hours, 1 day, 7 days, 14 days, and 40 days | 40 days |
Alarm details
On the" Monitoring" page of the instance, click "Alarm Details" to go to the instance "Alarm Management" page.
- Add alarm policy
After clicking "Alarm Details" to go to the instance "Alarm Management" page, click "Add Policy" to add the alarm policy. After entering the page below, define the policy's specific flow.
- View the alarm policy
Click "Alarm Event" to view the alarm event arising from this instance.
- Add alarm action
Click "Alarm Action" to go to the page for adding an alarm action, and you can add an alarm action according to your demands.
Click "Create Action" to go to the page for creating an alarm action, and you can create a specific action name and select an availability region on this page. Also, you can select the means of notice for this alarm action. Presently, Baidu AI Cloud supports "Mail Notice", "SMS Notice", and "Mail + SMS Notice". Meanwhile, you can create "Notice Object", and "User Group" and "User" are supported here. If you have no created notice object now, you are advised to click "Add User Group" for creation.
For details on alarm management, you can refer to "BCM Operations Guide-Management Alarm". After the successful creation of the RDS instance, two alarm policies (namely, CPU usage rate policy and data disk space usage rate policy) are provided by default, and you can edit and delete them.