This topic describes OCP-Agent and OB-Agent processes.
OCP-Agent processes
| Process name | Function | How to start and stop |
|---|---|---|
| pos_proxy | Provides OCP-Server with the capability of running remote commands through RPC. | The process automatically starts after a host is added. |
| node_exporter | A third-party component for collecting host hardware specifications. | The process automatically starts after a host is added. |
| ocp_agentd | OCP-Agent deamon process. | The process automatically starts when the OCP-Agent process starts, and automatically stops when there is no process for it to guard. |
Note
If you use the start command of the helper script to start the OCP-Agent service, the processes above are also started.
OB-Agent processes
| Process name | Function | Description |
|---|---|---|
| ob_agentd | OB-Agent deamon process. | The process automatically starts when the OB-Agent process starts. |
| obstat | Supports top SQL and RPC monitoring, as well as wait event and latch monitoring. | The process runs after OBServer is deployed. |
| ob_sql | Supports top SQL monitoring. | The process runs after OBServer is deployed. |
| ob_sql_audit | Supports slow SQL queries monitoring. | The process runs after OBServer is deployed. |
| ob_logtailer | Generates alerts according to OBServer logs. | The process runs after OBServer is deployed. |
| ob_cleaner | Clears OBServer log files. | The process runs after OBServer is deployed. |
| ob_exporter_1 | Supports second-by-second OBServer metric monitoring. | The process runs after OBServer is deployed. |
| ob_exporter_60 | Supports minute-by-minute OBServer metric monitoring. | The process runs after OBServer is deployed. |
| node_exporter_wrapper_ob | Supports monitoring of hardware metrics related to OBServer based on node_exporter. | The process runs after OBServer is deployed. |
| node_exporter_wrapper_obproxy | Supports monitoring of hardware metrics related to OBProxy based on node_exporter. | The process runs after OBProxy is deployed. |
Note
- If you use the start command of the helper script to start the ob_monitor service, all processes above except node_exporter_wrapper_obproxy are started.
- If you use the start command of the helper script to start the obproxy_monitor service, the node_exporter_wrapper_obproxy process is started, and the ob_agent process is also started if it has not been started already.