Let’s start node_exporter: # systemctl enable node_exporter # start on future boots Tell systemd to read this new file: # systemctl daemon-reloadĪlso create an options file /etc/default/node_exporter with the following contents: OPTIONS='' 3 Start node_exporter Use a text editor to create a systemd unit file /etc/systemd/system/node_rvice with the following contents: ĮnvironmentFile=/etc/default/node_exporterĮxecStart=/opt/node_exporter/node_exporter $OPTIONS Stop here if you are upgrading and go to the Start node_exporter section The logical link allows us to create systemd unit file without needing to update it each time we upgrade node_exporter. If node exporter was already installed, then remove the logical link first: # cd /optĪnd, now create the logical link to the current node_exporter version: # ln -s node_exporter-X.Y.Z.linux-amd64 /opt/node_exporter We are assuming you are doing these exercises as the root user or using the sudo command as needed.įetch and unpack the latest release from the releases page and create a symlink so that /opt/node_exporter refers to the current version. You should go here first and then replace the “X”, Y" and “Z” below in the link with the current Prometheus version number that is listed on the releases page (scroll down a bit to find the link). (If node_exporter is pre-installed and you are not upgrading, skip to the next section “Start node exporter”) This is much easier to configure and manage than SNMP.ĭo this on your campus server instance (.) 2 Install (or upgrade) node_exporter To collect metrics from Linux services, such as memory/CPU/disk utilisation, you install the node_exporter on each server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |