This docker image contains all the dependencies needed for a bosun server. It is designed for test use and is not suitable for production use since data is not persisted. OpenTSDB and HBase can take 15 or more seconds to initialize after the image is running.
Supported Tags and Release Notes:
$ docker run -d -p 4242:4242 -p 8070:8070 stackexchange/bosun
Bosun should now be running on port 8070 on your docker host (use -p 80:8070 if you want to serve via port 80 instead). OpenTSDB's interface can be accessed on port 4242. You can also use -p 5252:5252 to expose the internal tsdbrelay instance (for external counters), -p 9565:9565 to allow access to the ledis instance, or -p 16010:16010 to allow direct access to hbase.
In order to log data from other hosts in your environment, you will need to invoke scollector with the
Updating Bosun binary
To update the bosun binary without losing existing data, first enter the docker instance:
docker exec -it <id> bash where <id> is the id or name of the docker container running bosun. Determine which bosun release you want at https://github.com/bosun-monitor/bosun/releases and copy the URL to the linux-amd64 release. From inside the docker container, run:
$ apt-get update && apt-get install -y wget $ wget -O /bosun/bosun <bosun-release-URL> $ kill -HUP 1
Where <bosun-release-URL> is from the github releases page. The
kill -HUP 1 restarts supervisord and all its processes.
You really ought to tag specific versions. Otherwise, who knows if my "latest" is the same as the real "latest".
This image seems to deploy artifacts/dependencies that are based on java. They might have done better to use a different storage engine.