Monitor External Hosts
To monitor independent servers outside the Ops Platform deployment node (such as standalone database or cache nodes), install Node Exporter on those servers, and then add each one as a "Host" data source in the UI "Data Sources" page.
HAP/HDP standalone and cluster deployments already include ops-nodeagent (automatically listening on :59100). No action is required. Repeated installation will cause port conflicts. Only additional external hosts need the following steps.
-
Download and extract (the offline package is in the
common/directory; the version is the same as the one built into the image:1.8.2):wget https://pdpublic.nocoly.com/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 auto-start:
systemctl daemon-reloadsystemctl enable --now node_exportersystemctl status node_exporter -
In the UI "Data Sources" page, create a "Host" data source and enter the address, such as
192.168.1.20:59100(one entry per host). The change takes effect within 30 seconds after saving. You can then view it under "Resource Monitoring → Host" without restarting any container.If there are many hosts, use "Batch Import". The
hostInstancesection in the YAML template is:sources:- kind: hostInstancename: extra-node-01address: 192.168.1.20:59100purposes: [metrics]