This docker-compose permits to run:
- a cachet instance to display component status and metrics
- the cachet plugin cachet-url-monitor to automatically check components and update status and metrics
Both dockers are launch in a private docker network (172.0.3.0/24
by default).
This permits to isolate them. Cachet will be reachable on 172.0.3.2:8000
.
- git
- docker
- docker-compose
-
Update submodule for cachet and monitor
git submodule init git submodule update
-
Build the docker-compose:
docker-compose build
-
Launch cachet (this should not work):
docker-compose up cachet
-
Get the APP_KEY and add it in .env file
-
Re-launch Cachet (in detached mode this time):
docker-compose up -d cachet
-
Configuration via the web interface (172.0.3.2:8000). If you don't now for drivers, use
APC(u)
andSynchronous
. -
Connect to Cachet and create components and metrics used by the monitor
-
Get the token of the user (in 172.0.3.2:8000/dashboard/user)
-
Modify on the monitor configuration file monitor-config.yml:
- the
api_url
- the token
- the
-
Start the monitor:
docker-compose up -d monitor
- The first launch is not easy. The Cachet server need an encryption key
generated by the Cachet container. Also, the monitor need a token (to modify
the status) that is generated once the Cachet server is launched. Once the
APP_KEY and the token is filled, services can be manage normally with the
docker-compose
commands (up
,down
...) - One can use, mtakaki docker containers. This repo build the monitor docker, this permits to use it other architecture (like ARM with a Raspberry Pi).
- Data is saved in
data
folder.
- Wait that Cachet API is ready before launching the monitor
- Fill the BDD with monitor configuration
- Use
.env
to gather parameters - Change the queue system (something else than sync)