ZenPack:Docker

From Zenoss Wiki
Revision as of 06:22, 8 November 2014 by Vsergeyev (Talk | contribs)$7

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Author(s)
Volodymyr Serheiev
Current Maintainer(s)
Volodymyr Serheiev
License
Apache License, Version 2.0
ZenPack name
ZenPacks.community.Docker
More Information
GitHub page/HomePage
Git sources (for cloning)
Link


Applications Monitored: 



Docker ZenPack

Docker monitoring zenpack for Zenoss. Adds "Docker Containers" component to devices.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.

Releases

Version 1.0.0- Download
Released on 2014/11/08
Compatible with Zenoss Core 4.2.x, Zenoss Resource Manager 4.2.x

Background

Adds modeler plugin and monitoring datasource to retrieve list of Docker containers and monitor their statuses.

Docker Containers modeled in Zenoss device

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.Docker-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone https://github.com/vsergeyev/ZenPacks.community.Docker.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.Docker
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus