Monitor External Hosts
To monitor independent servers outside the Ops Platform deployment node, such as database or cache nodes, install Node Exporter on the target server, then add the host on the "Data Sources" page.
The Ops Platform's standalone deployment node and Kubernetes cluster nodes already run ops-nodeagent, which listens on :59100 automatically. Installing it again may cause port conflicts. These steps apply only to additional external hosts.
-
Download and extract Node Exporter on the target server. The offline package is in
common/, with the same version1.8.2as the image:wget https://pdpublic.mingdao.com/private-deployment/offline/common/node_exporter-1.8.2.linux-amd64.tar.gztar xvf node_exporter-1.8.2.linux-amd64.tar.gzmv node_exporter-1.8.2.linux-amd64 /usr/local/node_exporter -
Register the Systemd service:
cat > /etc/systemd/system/node_exporter.service <<'EOF'[Unit]Description=Node ExporterAfter=network.target[Service]User=rootType=simpleExecStart=/usr/local/node_exporter/node_exporter --web.listen-address=:59100Restart=alwaysRestartSec=3[Install]WantedBy=multi-user.targetEOF -
Start the service and enable startup at boot:
systemctl daemon-reloadsystemctl enable --now node_exportersystemctl status node_exporter -
Create a "Host" data source on the "Data Sources" page, one per server. Enter the target IP and port
59100, such as192.168.1.20:59100. Changes take effect within 30 seconds after saving. View the host in "Resource Monitoring → Host" without restarting containers.For many hosts, use "Batch Import". Example
hostInstanceentry in the YAML template:sources:- kind: hostInstancename: extra-node-01address: 192.168.1.20:59100purposes: [metrics]