Description
This alert is triggered when a scale-in failure is found in OBProxy console logs in OBSharding mode.
Principle
| Parameter | Value |
|---|---|
| Metric | instance_compress_failed_count |
| Source | This metric is collected from the OBProxy console logs. The metric shows the number of scale-in failures recorded in the logs. The related keyword in the log is release 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_compress_failed_count > 0 | The number of scale-in failures. | 0 | 60 seconds | 5 minutes |
Alert information
| Trigger method | Alert level | Scope |
|---|---|---|
| Based on the expression of the metric | Critical | OBProxy service |
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_compress_failed
- Details
- Template: OBProxy instance: ${obproxy_cluster}, deployment unit: ${host}], alert: Failed to release the deployment unit from the instance.
- Example: OBProxy instance: odp-tx9ympkg37m4, deployment unit: xxx.xxx.xxx.xxx, alert: Failed to release the deployment unit from the instance.
Impact on the system
If an OBProxy instance fails to be scaled in, resources cannot be released and will be wasted.
Possible causes
None.
Solutions
Collect OBProxy console logs and contact OceanBase technical support for troubleshooting.
