OceanBase Cloud Platform (OCP) provides you with alert monitoring services at the OceanBase cluster, tenant, and host levels. You can use the built-in alerts to meet your basic alert requirements. This topic helps you understand the built-in alerts.
The following table lists the components of each alert.
| Component | Description |
|---|---|
| Description | Describes the meaning of each alert and its trigger conditions. |
| Principle | Introduces the principle of an alert, especially the source of a metric value. The principle of an expression-triggered alert is described by using the following terms:
|
| Alert rule | Introduces the trigger rule of each alert, including metric, default threshold, source, duration, detection cycle, and time before clearance.
|
| Alert information | Describes the trigger method, alert level, scope, and target of each alert. The following alert trigger methods are supported:
|
| Alert templates | Describes the overview and details templates of each alert, and provides an example for each template. |
| Impact on the system | Describes the impact that may be caused on the system when the alert is triggered. |
| Possible causes | Describes the possible causes of an alert to help you locate and handle the alert. |
| Suggested solutions | Shows you how to solve the problems that caused the alert. |
When the default threshold cannot meet your requirement, you can modify the alert thresholds. For more information, see Modify alert thresholds. When you do not want to receive some alerts, you can block them. For more information, see Set an alert-blocking condition.
Concepts
Alert target
An alert target is a target that is monitored by the alert task and uniquely identifies an alert. It can be an OceanBase cluster, a server, or a service.
Based on the alert item, an alert target can be a tag value or a combination of tag values, such as obregion=obocp:svr_ip=*.*.*.* identifies a server in the OceanBase cluster or OCP cluster.
Alert scope
The alert scope defines the scope of an alert and is consistent with the metric scope. For example, when the CPU utilization exceeds the threshold, it can be a problem for the entire cluster, the tenant, or a single server.
The alert scope includes an OceanBase cluster (OBCluster), a tenant in the OceanBase cluster (OBTenant), an application cluster (AppCluster), a service, a host, and a process. The process is reserved.
Alert level
Each alert item has an alert level.
| Alert level | Meaning | Color | Description |
|---|---|---|---|
| 1 | Stopped | Purple | The system is completely unavailable and needs immediate recovery. For example, An OceanBase Database service cannot be started. |
| 2 | Critical | Red | The system availability decreases and the necessary measures must be taken to prevent the system from becoming completely unavailable. For example, The memory usage of a server exceeds the threshold of 90% and this condition has lasted for 3 minutes. |
| 3 | Warning | Orange | The system is still available but it is about to become unavailable. You must take measures to prevent the reduction of availability. For example, The proportion of connections of an OceanBase Database tenant exceeds the threshold of 80%. |
| 4 | Caution | Blue | Based on the trend, you can see that the important performance metrics of the system are declining. You can locate potential problems by using troubleshooting methods to avoid triggering alerts. This alert level is reserved but no alert item matches this level at present. |
| 5 | Reminder | Green | Technically, a reminder is not an alert. It usually indicates that an administrator has performed an important action. For example, The administrator deleted a cluster. After alerts at this level are cleared, no notification is generated. |