Description
This alert is triggered when a scale-out failure is found in the OBProxy console logs in OBSharding mode.
Principle
| Parameter | Value |
|---|---|
| Metric | instance_expanse_failed_count |
| Source | This metric is collected from the OBProxy console logs. The metric shows the number of scale-out failures recorded in the logs. The related keyword in the log is create instance unit is failed. |
| Collected metric | None |
| Metric expression | None |
| Collection cycle | 1 minute |
Alert rule
| Metric expression | Metric description | Default threshold | Detection cycle | Elimination cycle |
|---|---|---|---|---|
| instance_expanse_failed_count > 0 | The number of scale-out failures on an OBProxy instance. | 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_instance_expanse_failed
- Details
- Template: OBProxy instance: ${obproxy_cluster}, deployment unit: ${host}], alert: Failed to add the deployment unit to the instance.
- Example: OBProxy instance: odp-tx9ympkg37m4, deployment unit: xxx.xxx.xxx.xxx, alert: Failed to add the deployment unit to the instance.
Impact on the system
If the scale-out of an OBProxy instance fails, the impact varies based on the actual situation.
Possible causes
None.
Solutions
Collect OBProxy console logs and contact OceanBase technical support for troubleshooting.