Description
This alert is triggered when the OBProxy is disconnected.
Principle
The following table describes the key parameters that are involved in the monitoring and alerting logic.
| Parameter | Value |
|---|---|
| Metric | obproxy_connectable |
| Source | OCP-Agent checks the local OBProxy connectivity by establishing a socket connection to localhost:2883. The timeout value is 0.8s. |
| Collected metric | obproxy_connectable |
| Metric expression | obproxyd_process_exists{app="ODP",@LABELS} |
| Collection cycle | 1 second |
Note
The metric source of this alert is special. OCP-Agent checks the local OBProxy connectivity by establishing a socket connection to localhost:2883 and returns the result to the collected metric.
The port number 2883 in the Source row is obtained by querying the /home/admin/ocp_agent/config.conf file.
The value of the metric obproxy_connectable indicates the OBProxy connectivity. Valid values: 1 and 0. The value 1 indicates that the OBProxy is connectable and 0 indicates that it is unconnectable.
The alert is triggered when the value of the metric is 0.
Alert rule
| Metric | Default threshold | Duration | Detection cycle | Time before clearance |
|---|---|---|---|---|
| obproxy_connectable | 0 | 0 seconds | 10 seconds | 5 minutes |
Alert information
| Trigger method | Alert level | Scope |
|---|---|---|
| Metric expression | Stopped | Server |
Alert templates
Overview: ${alarm_target} ${alarm_name}
Details: ${alarm_target} ${alarm_name}
Overview example: obproxy_cluster_id=3:obproxy_cluster=obproxy_02:svr_ip=192.168.1.1. The OBProxy is unconnectable.
Details example: obproxy_cluster_id=3:obproxy_cluster=obproxy_02:svr_ip=192.168.1.1. The OBProxy is unconnectable.
${alarm_target} indicates the object that generated the alert, in the obproxy_cluster_id=xx:obproxy_cluster=xx:svr_ip=xx format. obproxy_cluster_id indicates the ID of the OBProxy cluster that generated the alert. obproxy_cluster indicates the name of the OBProxy cluster that generated the alert. svr_ip indicates the IP address of the OBProxy server that generated the alert.
Impact on the system
OBProxy provides access to the OBServer cluster as the proxy. When OBProxy is not connected, the application cannot connect to the database.
Possible causes
This problem is commonly found in the following scenarios:
A network communication error occurs.
The obproxy process unexpectedly stops.
Suggested solutions
Check the causes of OBProxy disconnection and recover the connection.
If the OBProxy server is damaged, replace it with a new one.
If the OBProxy node is no longer needed, you can delete it.
If a process exception occurs, see ob_cannot_connected.