Browse Source

Forgot role..

pull/8/head
Egon Rijpkema 4 years ago
parent
commit
3dd30c02fe
  1. 2
      documentation/prometheus.md

2
documentation/prometheus.md

@ -5,7 +5,7 @@ Below is a picture of the current prometheus monitoring setup on gearshift. Our @@ -5,7 +5,7 @@ Below is a picture of the current prometheus monitoring setup on gearshift. Our
## Node exporter
Each peregrine node has a node exporter running. It was installed using the node exporter.yml playbook in the root of this repository.
This playbook applies the node exporter which does little more than copy the binary (from promtools/results) to the node and install a systemd unit file on the node. The node exporter listens for requests on port 9100 on each node.
This playbook applies the node exporter role which does little more than copy the binary (from promtools/results) to the node and install a systemd unit file on the node. The node exporter listens for requests on port 9100 on each node.
## Prometheus server
The server runs in a docker container on knyft. It was installed using the prometheus.yml playbook that installs the prom_server role. This role also contains its configuration files. The server scrapes the exports of the nodes. It stores them in a special time series database that is integrated in the prometheus server. Targets and alerts are configured using these files. Prometheus also has a web frontend that listens on [knyft](http://knyft.hpc.rug.nl:9090/graph) and is accessible from the management vlan. Via the webinterface it is possible to query the data directly and to see the status of reporters to the server. Alerts are also shown here.

Loading…
Cancel
Save