You are here

Integrations

Docker

Download version    6.0    5.x

Included in Opsview Monitor 5.x
Included in Opsview Monitor 6.0
check_circle
Opsview Supported

Docker Opspack

Docker exists as an open platform for developers and sysadmins to build, ship, and run distributed applications. Docker containers are helping drive the micro services movement by making portable, easily deployable containerized systems which are both easy to build and maintain.

Docker utilizes containers which use shared operating systems that don’t take up a large amount of system resources. And since Docker is comprised of open source and commercial technologies, it achieves application portability across multiple environments. Linux containers have been around for years, but Docker brings them to the masses and makes them standardized and easy to use.

What You Can Monitor

Our Opspack allows you to pull vital information from all of your containers and makes sure they are up and running, allowing you to monitor their resource usage such as CPU, size and memory. It also gives users the ability to monitor Docker on a per container basis, returning system statistics including container size (MB/GB), container uptime and the ‘top’ command output for each container where possible.

Service Checks

Service Check Description
Container CPU usage Measures the CPU usage of each container on the Docker host
Container memory usage Measures the memory usage of each container on the Docker host
Container size Measures the size in MB/GB of each container on the Docker host
Container top output Returns the 'top' command output for the given container
Container uptime Measures the uptime of each Docker instance on the Docker host
List all containers Returns a list of all containers on the Docker host which the template is applied to
Overall status Returns three values: total number of containers running, total number stopped and total number overall of containers running on the specified Docker host

Docker Opspack

Docker exists as an open platform for developers and sysadmins to build, ship, and run distributed applications. Docker containers are helping drive the micro services movement by making portable, easily deployable containerized systems which are both easy to build and maintain.

Docker utilizes containers which use shared operating systems that don’t take up a large amount of system resources. And since Docker is comprised of open source and commercial technologies, it achieves application portability across multiple environments. Linux containers have been around for years, but Docker brings them to the masses and makes them standardized and easy to use.

What You Can Monitor

Our Opspack allows you to pull vital information from all of your containers and makes sure they are up and running, allowing you to monitor their resource usage such as CPU, size and memory. It also gives users the ability to monitor Docker on a per container basis, returning system statistics including container size (MB/GB), container uptime and the ‘top’ command output for each container where possible.

Service Checks

Service Check Description
Container CPU usage Measures the CPU usage of each container on the Docker host
Container memory usage Measures the memory usage of each container on the Docker host
Container size Measures the size in MB/GB of each container on the Docker host
Container top output Returns the 'top' command output for the given container
Container uptime Measures the uptime of each Docker instance on the Docker host
List all containers Returns a list of all containers on the Docker host which the template is applied to
Overall status Returns three values: total number of containers running, total number stopped and total number overall of containers running on the specified Docker host

Setup and Configuration

To configure and utilize this Opspack, you simply need to add the 'Application - Docker' Opspack your Opsview Monitor system.

Step 1: Configure Docker to allow monitoring

To enable the Docker API on Debian / Ubuntu (which uses systmctl, rather the /etc/init.d scripts), we had to modify the file:

/lib/systemd/system/docker.service

to change the execute line to:

ExecStart=/usr/bin/docker -d -H 127.0.0.1:4243 -H unix:///var/run/docker.sock

This makes the demon start listening on port 4243 (note: we have only shared this locally as it is not secure in this state).

Docker 1.5+ update: After upgrading to the latest version (1.5.0), these settings were overwritten. After re-enabling them, we had to run the command "systemctl daemon-reload" to make them take effect.

For older operating systems, you will need to modify the file:

/etc/default/docker

To add, modify the line DOCKER_OPTS to:

DOCKER_OPTS="--dns 8.8.8.8 -H 127.0.0.1:4243 -H unix:///var/run/docker.sock"

You can change the DNS server to suit your environment and then restart the Docker service. These steps enable the plugin to connect and monitor Docker. We recommend only exposing Docker on 127.0.0.1 for security purposes.

Step 2: Add the host template

Add Opspack to host

Step 2: Add and configure variables required for this host

Configure host variables

Step 3: Reload and the system will now be monitored

View host service checks

Setup and Configuration

To configure and utilize this Opspack, you simply need to add the 'Application - Docker' Opspack your Opsview Monitor system.

Step 1: Configure Docker to allow monitoring

To enable the Docker API on Debian / Ubuntu (which uses systmctl, rather the /etc/init.d scripts), we had to modify the file:

/lib/systemd/system/docker.service

to change the execute line to:

ExecStart=/usr/bin/docker -d -H 127.0.0.1:4243 -H unix:///var/run/docker.sock

This makes the demon start listening on port 4243 (note: we have only shared this locally as it is not secure in this state).

Docker 1.5+ update: After upgrading to the latest version (1.5.0), these settings were overwritten. After re-enabling them, we had to run the command "systemctl daemon-reload" to make them take effect.

For older operating systems, you will need to modify the file:

/etc/default/docker

To add, modify the line DOCKER_OPTS to:

DOCKER_OPTS="--dns 8.8.8.8 -H 127.0.0.1:4243 -H unix:///var/run/docker.sock"

You can change the DNS server to suit your environment and then restart the Docker service. These steps enable the plugin to connect and monitor Docker. We recommend only exposing Docker on 127.0.0.1 for security purposes.

Step 2: Add the host template

Add Opspack to host

Step 2: Add and configure variables required for this host

Configure host variables

Step 3: Reload and the system will now be monitored

View host service checks

v1.0-opsview-5

ODI-604 Release Opspacks to GitHub

Initial upload of existing Opspacks to GitHub

v2.0-opsview-6

ODI-1154 Release Opspacks for Opsview Monitor 6.0

Initial release of Opspack to work with Opsview Monitor 6.0