Prometheus is a very nice open-source monitoring system for recording real-time metrics (and providing real-time alerts) in a time-series database for a variety of purposes.
Here we're going to setup Prometheus on a server to monitor a wealth of statistics (such as CPU/memory/disk usage, disk IOps, network traffic, TCP connections , timesync drift, etc.) as well as monitor several endpoints (which could be web applications or services like bitwarden, rocketchat, gitlab, etc.).
We'll also setup a simple dashboard with Grafana, another (great) open-source visualisation and analytics platform that integrates fantastically with (and out-of-the-box) with Prometheus. This will provide a nice dashboard that we'll use to quickly see the status of the endpoints we're monitoring.
An example can be seen at https://mon.jaytaala.com.
A bit about Blackbox Exporter, Node_Exporter and Grafana...
Blackbox exporter is a prometheus exporter which can probe endpoints via http/https, icmp, etc. It's extremely simple to setup and can be used to monitor the status of various endpoints (which could be web applications, REST endpoints, etc.).
We've already setup
blackbox-exporter in our prometheus configuration file (see lines 36 to 57).
node_exporter is a prometheus exporter which monitors hardware and 'nix OS metrics. It runs on a port exposed to prometheus and prometheus can then query it and get a (large) ranger of metrics for whatever machine is running node_exporter.
Grafana is a great platform for visualising data and metrics from large data sets. It can connect with a very large number of data sources and has native (built-in) prometheus support, which makes it extremely easy to integrate prometheus and provides an attractive and versatile front-end to view various prometheus metrics.
We'll cover the following steps:
Installing and configuring Prometheus, Blackbox exporter, and Grafana with Docker-Compose
Thanks to Docker and Docker Compose, we'll only need to run a single command to deploy Prometheus, an exporter (which can query endpoints), and Grafana. Let's start by cloning our setup files from my git repo:
The repo contains several files:
- blackbox-exporter.yml : configuration file for blackbox-exporter
- dashboard-blackbox.json : blackbox exporter dashboard I've customised see Adding monitoring dashboards;
- dashboard-node_exporter.json : node_exporter dashboard I've customised see Adding monitoring dashboards;
- docker-compose.yml : docker compose config file
- grafana.ini : grafana configuration file
- prometheus.yml : prometheus configuration file
Once you've cloned the repo, simply run (from the with the cloned folder:
If things worked as they should you should be able to visit the basic Grafana web interface at http:\\<INTERNAL-SERVER-IP>:3000.
Replace <INTERNAL-SERVER-IP> with the actual internal IP address of your server, e.g. 192.168.1.x, 10.0.0.x (or whatever it is).
That's it! that wasn't so bad was it?
If it fails it's most likely that port 3000 on the host is taken - in which case simply change the "ports" first value in docker-compose.yml to another port. E.g. for me I used:
Optional reading (explanation of configuration files)
Explanation of prometheus.yml
This file is the main Prometheus.yml scrape configuration file. It defines things like how often Prometheus should scrape (query) data and from where (and how) it should scrape this data.
|1-5||Default scraping config for how often Prometheus should scrape. Note, these can be overridden for specific scrape configs (see from line 22).|
Prometheus (be default) monitors itself and can report on scrape query duration, samples added to db, data compaction stats etc.
Scrape configutation for node_exporter, an exporter which scrape server machine metrics. We haven't set this up yet but will in the following sections.
This is NOT localhost (localhost in this context is the Prometheus Docker container).
Scrape configuration for blackbox, a prober that can probe endpoints over HTTP, HTTPS, DNS, TCP and ICMP. We haven't set this up yet but will in the following sections.
Explanation of grafana.ini
This file is the main grafana config file for our setup. It defines things server related settings, as well as settings we'll use to enable public viewing access.
|1-2||Defines server settings for our setup - including the port to bind/ and our domain name.|
Settings to enable anonymous (public) viewer access to any dashboards you give
You'll note that I've defined my domain as
mon.jaytaala.com. This is an external address for which I'm using a reverse proxy to secure (SSL) and route traffic to the internal 4000 port of Grafana. See Apache reverse-proxy SSL to multiple server applications for more information on how to implement this.
Installing and configuring node_exporter (to monitor server stats)
By default node_exporter enables a large number of "collectors" (modules which collect certain information from the machine). See here for a list of collectors enabled by default (and what info they collect).
node_exporter can be run from a docker container, but it's not recommended since it should be run directly on the host hardware to collect stats.
Installing node_exporter can be done by downloading a recent version version, untar'ing and executing. We're going to be doing an extra step here to manage node_exporter with systemd (so it starts on server boot etc.).
We start with downloading. You can find a link for the latest version at https://prometheus.io/download/#node_exporter. At the time of this writing the latest stable version for linux-amd64 was node_exporter-0.18.1.linux-amd64.tar.gz.
We'll download, untar, and then move it to
With node_exporter installed let's make it easier to manage by creating a systemd service. Create a file in /etc/systemd/system/ with your favourite text editor (I'm using vim here):
and paste the following:
I'm using a non-default port here (10091) so change it to whatever port you prefer (or have free).
Finally let's enable it (to start on boot) and start the service
We've already setup node_exporter in our prometheus configuration file (see lines 31 to 34).
Setting up Grafana data sources and dashboards
Adding Prometheus as a data source to Grafana
Once you have your docker containers running, access port 3000 on the server with a browser (e.g. visit http://192.168.0.1:3000 or whatever your internal address is for your server).
Grafana's login screen should appear - if you're the first user to login after creating this container then just enter any new credentials.
Once actually logged in, click on the "add data source" and select "Prometheus":
You can leave most setting as default and simply enter the server url for the Prometheus instance we have setup, for my case it looks like:
The URL should point to the server's internal IP and NOT localhost (or 127.0.0.1) since
localhost from Grafana's point of view in is the Grafana docker container.
Adding monitoring dashboards
One of the great things with Grafana is that it is extremely easy to use (and publish) any dashboards that others have created. There's many (many) dashboards for different systems and many for prometheus and it's many exporters (like node_exporter, blackbox, etc.).
At mon.jaytaala.com I've used these dashboard (which I've then customised further to suit my needs):
- https://grafana.com/grafana/dashboards/7587 (for viewing blackbox http endpoint statuses);
- https://grafana.com/grafana/dashboards/1860 (for viewing server system stats);
You can see many other dasboards for grafana/prometheus here.
It's incredibly simple to add a dashboard to Grafana. Select the dashboards icon from the left menu and then select "Manage:
Now click the "import" button:
Either copy the link (e.g. https://grafana.com/grafana/dashboards/7587) or simply note the dashboard number (7587). Enter this into the "Grafana.com Dashboard" input and press the tab key:
You can also add dashboard via by uploading a dashboard .json. You'll note that I have two dashboard .json files in the repository - you can upload these by clicking the "Upload .json file" button.
Grafana will grab the dashboard and after a second or so will fetch the dashboard ready for importing. Enter a few options (see arrows) and then click "Import":