The docker-prometheus repository is meant to support an introduction
to the Prometheus monitoring tool described in this
blog post. It will only work on a single node.
Additionally this repo provides code for a way to use both a local default configuration and dynamic configuration stored in a dedicated data container.
You can run this container out of the box to simply play with the Prometheus UI. More interesting however is using the dedicated configuration container found here to create look at container metrics.
The prom/prometheus container is extended with a simple configuration that
is meant to show the service is up and allow an exploration of the GUI.
To run this container you need only execute the command:
docker run \
--detach \
--name prom-server \
--publish 9778:9090 \
behemphi/prometheus \
-config.file=/prom-config.yml
You can explore the basics of the Prometheus UI now by going to
http://nodeIP:9778. Check the above referenced blog for more detail.
Note: The host port is changed because 9090 is too common a choice for web apps.
To run cAdvisor and Prometheus server in your StackEngine CAC:
- Start a new app by clicking the Applications item on the left menu
- Name your app and click "Save"
- Click "Create First Version"
- Click the "Advanced Editor" in the upper right
- Copy and paste the contents of
stack.yml, then click "Apply" - Click "Save" in the upper right corner
- Click the green "Launch" button, Tag the image and Click "Launch" again
- Name the Instance, choose the Tag and Pool (Deploy To), then Click "Launch"
Navigate your browser to http://nodeIP:9778 and to see Prometheus functioning.
Prometheus keeps a list of nodes it is polling in its configuraiton file.
This makes for an extremely volatile config in an environment of any size.
The approach here takes the view that hosts are stabe enough that the config file can be managed through source control.
Because there are two containers needed to run Prometheus start the server
with docker-compose:
docker-compose up -d
If you are cycling quickly as you play around, it's a good idea to use the
--force-recreate flag as well.
If your particular situation is such that hosts are volatile then we recommend
a solution with confd. Pull requests are welcome if you would like to
add such a solution to this repo!
Three are a number of strong assumptions here about ports, names and the like. Please play all you like, improve with pull requests, etc. But understand that, for now, the purpose is to provide you a template for getting started.
MIT