docker-compose is the recommended way to quickly experiment with and
develop against Monasca. To get started, you’ll need a Docker environment with:
monasca-docker repository and run
If all goes well, the full Monasca pipeline should start within (roughly) one minute. The following services should be exposed on your host machine:
Note that the docker-compose environment currently does not start any Agent instances. There will be few (if any) metrics going through the pipeline, though it should otherwise be working.
You can the status of each component by running
docker-compose ps (you will
probably need to run this in a separate shell unless you ran
docker-compose up -d). If everything started successfully, it should look like
Note that several initialization jobs are run on new deployments, so it’s normal
to see containers with an
Exit 0 state. See below for troubleshooting failed
Failed init jobs will appear in
docker-compose ps with a nonzero exit code.
Occasionally jobs will fail due to timeouts, especially on systems with limited
CPU. In these cases it is probably safe to re-run the job by simply running
docker-compose up again. This will re-run all of the jobs, but only those that
failed to complete will actually modify the deployment.
If the jobs are still failing, you can view the log output of each job using
docker-compose logs [job name], where
[job name] is one of
log output should provide some reason for the failure that can be included in a