Monitoring Docker with docker-scout
When it comes to agent-based monitoring and Docker, you're typically choosing between two bad options: (1) install the agent and its dependencies directly on the host or (2) running an agent in every container.
- Installing the agent on the host is bad: Docker is best when everything is containerized. It means your services will run as expected, anywhere, without dependencies. Why does monitoring get to break that rule?
- Running an agent in every container is bad: lets say you have 30 containers on a host that need to be monitored. Do you really want 30 agents running (one in each container)? That's a considerable amount of overhead.
1. Create a configuration file
Create a file called
scoutd.yml (or copy our template). Your account_key is required, all other values are optional.
2. Run the docker image
Run the scout image, mounting the
scoutd.yml file. Running the image will first download the image, if it is not already locally available. Run the following command in the directory containing your
docker run -d --name scout-agent \ -v /proc:/host/proc:ro \ -v /etc/mtab:/host/etc/mtab:ro \ -v /var/run/docker.sock:/host/var/run/docker.sock:ro \ -v `pwd`/scoutd.yml:/etc/scout/scoutd.yml \ --net=host --privileged scoutapp/docker-scout
Monitoring Docker Containers
Monitor the resource usage of your running containers with our Docker Monitoring Plugin
Questions? Using Docker?
Shoot us an email at firstname.lastname@example.org or open an issue.