Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This script simply creates (and/or runs) our Prometheus container.  So what's going on here?

...

View Git file
pathrun-container.sh
repository-id8
languagebash
branchrefs/tags/documented
linenumberstrue

Line(s) numberComment
1bash script header (tells shell that it's a bash script when it gets executed)
2

removes / deletes the container.  This deletes the already running container (if it exists) before creating a new one.

Tip

Don't worry(!) our data won't be lost since we're persisting the Prometheus data with a Docker data volume!


3

main docker run command.

The -d flag means "detached" (i.e. run it detached or in the background) and the --name=prom names the container that will be created "prom".

4

this data-binds our prometheus.yml config file to /etc/prometheus/prometheus.yml in the created Docker container.  I.e. prometheus running in the container will use this file for it's configuration.

5

this instructs Docker to create a data volume (for storing our persistent Prometheus data) and call it "prom-data".

It's kind of similar to a data-bind but it's managed by Docker and provides many advantages.

The actual files (and persistent data) can be found at:
/var/lib/docker/volumes/prom-data/_data

6

binds port 10090 on the host to post 10090 on the container (in other words exposes the prometheus port on the host).

Info

Note: this is not the default port for Prometheus (default port is 9090).  Change both of these to whatever port you would like to bind Prometheus to.

Also see line number 9 which would also need to match the port entered here.

You'll also need to modify the included prometheus.yml file and replace 10090 to whatever port you want to use.


7Tells Docker that this container should start/restart whenever Docker starts/restarts (for example on boot etc.).
8Points Docker to the official Prometheus image.  Docker will download this image if it hasn't already.
9-13Commands for configuration sent to the Prometheus executable in the container.  Most of these are pointing to the various locations were have previous bound with data-binds or data-volumes.
14Disabled.  Uncomment to enable the admin-api (so can accept POST queries to modify / delete data etc.).


Anchor
prometheus.yml
prometheus.yml
 (Optional Read) 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.

...

View Git file
pathprometheus.yml
repository-id8
branchrefs/tags/documented
linenumberstrue

Line(s) numberComment
1-5Default scraping config for how often Prometheus should scrape.  Note, these can be overridden for specific scrape configs (see from line 22).
23-29

Prometheus (be default) monitors itself and can report on scrape query duration, samples added to db, data compaction stats etc.

Info

Note that localhost:10090 refers to the Prometheus docker container and not the server.


31-34

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.

Info

Note that 10.0.0.137:10091 refers to the internal IP address of the machine you want to monitor (and the port on which node_exporter is running). 

This is NOT localhost (localhost in this context is the Prometheus Docker container).


36-57

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.

Info

Note that 10.0.0.137:9115 refers to the internal IP address and port of the machine on which blackbox is running on.  We'll be setting up blackbox on a docker container and then exposing port 9115 to the host. 

This is NOT localhost (localhost in this context is the Prometheus Docker container).



Updating Prometheus with Docker

...

Finally let's enable it (to start on boot) and start the service

Code Block
languagebash
sudo systemctl daemon-reload
sudo systemctl enable --now node_exporter

...