Changes for page Configuring a VPS machine from scratch

Last modified by Alexandru Pentilescu on 2024/07/22 21:37

From 9.1 to 10.1

From version 10.1

edited by Alexandru Pentilescu
on 2024/07/22 21:05

Change comment: There is no comment for this version

To version 12.1

edited by Alexandru Pentilescu
on 2024/07/22 21:37

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -163,6 +163,182 @@
  wget https://github.com/prometheus/node_exporter/releases/download/v0.15.2/node_exporter-0.15.2.linux-amd64.tar.gz
  {{/code}}
++Once this is done, extract the contents of the archive:
++
++{{code language="bash"}}
++tar -xf node_exporter-0.15.2.linux-amd64.tar.gz
++{{/code}}
++
++We will be running this as its own user. In order to avoid having to create a home directory for that user, it's best if we move the utilities that just got extracted to the root directories:
++
++{{code language="bash"}}
++mv node_exporter-0.15.2.linux-amd64/node_exporter /usr/local/bin
++{{/code}}
++
++Create the new user:
++
++{{code language="bash"}}
++useradd -rs /bin/false node_exporter
++{{/code}}
++
++Create a new systemd service file, that will start the node_exporter automatically, after each boot:
++
++{{code language="systemd"}}
++[Unit]
++Description=Node Exporter
++After=network.target
++
++[Service]
++User=node_exporter
++Group=node_exporter
++Type=simple
++ExecStart=/usr/local/bin/node_exporter
++
++[Install]
++WantedBy=multi-user.target
++{{/code}}
++
++Once this has been done, reload the service files, enable the newly created service and start it:
++
++{{code language="bash"}}
++systemctl daemon-reload
++systemctl enable node_exporter
++systemctl start node_exporter
++{{/code}}
++
++== Installing Prometheus ==
++Prometheus will be aggregating all the data that is collected by the node_exporter and allowing for it to be queried with a standardized syntax.
++
++To install Prometheus, we must first download it:
++
++{{code language="bash"}}
++wget https://github.com/prometheus/prometheus/releases/download/v2.1.0/prometheus-2.1.0.linux-amd64.tar.gz
++tar -xf prometheus-2.1.0.linux-amd64.tar.gz
++{{/code}}
++
++Much like with node_exporer above, we will force Prometheus to run as its own user, for security reasons. As such, we should isolate its files to the root filesystem:
++
++{{code language="bash"}}
++mv prometheus-2.1.0.linux-amd64/prometheus prometheus-2.1.0.linux-amd64/promtool /usr/local/bin
++{{/code}}
++
++We should also create new directories to store the relevant data for Prometheus:
++
++{{code language="bash"}}
++mkdir /etc/prometheus /var/lib/prometheus
++{{/code}}
++
++Then move the current directories to the appropriate system-level locations:
++
++{{code language="bash"}}
++mv prometheus-2.1.0.linux-amd64/consoles prometheus-2.1.0.linux-amd64/console_libraries /etc/prometheus
++{{/code}}
++
++== Configuring Prometheus ==
++Create a new /etc/prometheus/prometheus.yml with the following contents:
++
++{{code language="yml"}}
++global:
++  scrape_interval: 10s
++scrape_configs:
++  - job_name: 'node'
++    static_configs:
++      - targets: ['localhost:9100']
++{{/code}}
++
++Once the above is done, we should create the new prometheus user:
++
++{{code language="bash"}}
++useradd -rs /bin/false prometheussudo chown -R prometheus: /etc/prometheus /var/lib/prometheus
++chown -R prometheus: /etc/prometheus /var/lib/prometheus
++{{/code}}
++
++Then, please create an /etc/systemd/system/prometheus.service file with the following contents:
++
++{{code language="systemd"}}
++[Unit]
++Description=Prometheus
++After=network.target
++
++[Service]
++User=prometheus
++Group=prometheus
++Type=simple
++ExecStart=/usr/local/bin/prometheus \
++    --config.file /etc/prometheus/prometheus.yml \
++    --storage.tsdb.path /var/lib/prometheus/ \
++    --web.console.templates=/etc/prometheus/consoles \
++    --web.console.libraries=/etc/prometheus/console_libraries
++
++[Install]
++WantedBy=multi-user.target
++{{/code}}
++
++Then reload:
++
++{{code language="bash"}}
++systemctl daemon-reload
++systemctl enable prometheus
++systemctl start prometheus
++{{/code}}
++
++After everything has been done, we can proceed with Grafana itself.
++
++== Installing Grafana ==
++Ideally Grafana should be installed from its own APT repository, as this will keep it updated constantly. To do so:
++
++{{code language="bash"}}
++apt-get install -y apt-transport-https software-properties-common wget
++mkdir -p /etc/apt/keyrings/
++wget -q -O - https://apt.grafana.com/gpg.key | gpg --dearmor | tee /etc/apt/keyrings/grafana.gpg > /dev/null
++echo "deb [signed-by=/etc/apt/keyrings/grafana.gpg] https://apt.grafana.com stable main" | tee -a /etc/apt/sources.list.d/grafana.list
++apt-get update
++apt-get install grafana
++{{/code}}
++
++== Configuring Grafana ==
++After Grafana has been installed, we should make sure that it works properly by changing its default port from port 3000 to 4000 (as port 3000 is normally used by Gitea on our instance).
++
++To do so, please edit /etc/grafana/grafana.ini by uncommenting the following line and changing the port number to:
++
++{{code language="ini"}}
++http_port = 4000
++{{/code}}
++
++Once this is done, enable the grafana-server service and start it:
++
++{{code language="bash"}}
++systemctl daemon-reload && systemctl enable grafana-server && systemctl start grafana-server.service
++{{/code}}
++
++== Expose the newly created port as an nginx subdomain ==
++
++Finally, configure an nginx service file for it. Create an /etc/nginx/sites-available/grafana.conf file with the following contents:
++
++{{code language="nxinx"}}
++server {
++  server_name stats.transistor.one;
++
++  listen [::]:443 ssl http2; # managed by Certbot
++  listen 443 ssl http2; # managed by Certbot
++
++  include /etc/nginx/snippets/ssl.conf;
++
++  location / {
++    proxy_set_header Host $http_host;
++    proxy_pass http://localhost:4000;
++  }
++}
++{{/code}}
++
++Apparently the proxy_set_header directive is necessary to avoid some weird error when trying to set a new password.
++
++== Set up the environment ==
++From this point on, all that's left is to login to stats.transistor.one and set up a new account. The default credentials to do so are username: admin and password: admin. You should change those immediately so that they will not get abused.
++
++Once that's done, configure your own dashboard and make it work. Personally, I like to import a public dashboard called Node Exporter Full, which looks very cool.
++
++Happy coding!
  )))