Description
This alert is triggered when an SQL execution failure is found in an OBProxy log.
Principle
| Parameter | Value |
|---|---|
| Metric | sql_execute_failed_count |
| Source | This metric is collected from the OBProxy log obproxy_error.log. The metric shows the number of SQL execution failures. |
| Collected metric | None |
| Metric expression | None |
| Collection cycle | 1 minute |
Alert rule
| Metric expression | Metric description | Default threshold | Detection cycle | Elimination cycle |
|---|---|---|---|---|
| sql_execute_failed_count > 0 | The number of SQL execution failures. | 0 | 60 seconds | 5 minutes |
Alert information
| Trigger method | Alert level | Scope |
|---|---|---|
| Based on the expression of the metric | Critical | OBProxy |
Alert templates
- Overview
- Template: ${alarm_target} ${alarm_name}
- Example: alarm_template_id=0:odp_instance_id=odp-tx9ympkg37m4:host=xxx.xxx.xxx.xxx:odp_schema=obcluster:ocp_meta:test odp_sql_execute_failed
- Details
- Template: OBProxy instance: ${obproxy_cluster}, deployment unit: ${host}, database: ${odp_schema}, alert: The number of SQL failures is ${value}, which exceeds the threshold of ${alarm_threshold}.
- Example: OBProxy instance: odp-tx9ympkg37m4, deployment unit: xxx.xxx.xxx.xxx, database: obcluster:ocp_meta:test, alert: The number of SQL failures is 1, which exceeds the threshold of 0.
Impact on the system
The impact must be analyzed based on the actual situation.
Possible causes
None.
Solutions
Collect OBProxy logs and contact OceanBase technical support for troubleshooting.