Difference between revisions of "ZenPack:Availability Report Per Collection"

From Zenoss Wiki
Jump to: navigation, search
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
{{ZenPack
 
{{ZenPack
|Summary=This ZenPack extends Juerg Gerber's Availability Per Group Report, adding support for additional organizers.  You can now specify Group, System, Location and Device Class, in addition to the standard event availability report.  Both device id and title are output.  A sample reportmail script is provided in the libexec directory to directly email reports.
+
|Summary=This ZenPack extends Juerg Gerber's Availability Per Group Report, adding support for additional organizers.  You can now specify Group, System, Location and Device Class, in addition to the standard event availability report.
 
+
The 1.4.0 version is a major update and is based on code from Zenoss 4.2.5 SUP 671.
+
 
+
There are 2 branches; master outputs all fields; the title branch just outputs id, title, link and availability.
+
 
|Author=Jcurry
 
|Author=Jcurry
 
|Maintainer=Jcurry
 
|Maintainer=Jcurry
 
|Organization=Skills 1st
 
|Organization=Skills 1st
|License=GNU General Public License, Version 2
 
 
|ZenPack name=ZenPacks.community.AvailabilityReportPerCollection
 
|ZenPack name=ZenPacks.community.AvailabilityReportPerCollection
 
|Homepage=https://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection
 
|Homepage=https://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection
 
|Documentation URL=https://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection/blob/master/README.rst
 
|Documentation URL=https://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection/blob/master/README.rst
 
|Source URI=git://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection.git
 
|Source URI=git://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection.git
|Restart=Restart Zenoss.  Subsequent changes, you can probably get away with just bouncing zenhub and zopectl in a Core environment.
 
 
|Tags=require-extjs4-update, known-4x-compat-issue
 
|Tags=require-extjs4-update, known-4x-compat-issue
 
|Releases={{Release
 
|Releases={{Release
|Version=1.4.0
 
|Tag=da0adda42320311a1e5f6912d6d9c942f66122f3
 
|Release date=2016/08/11
 
|Summary=Code now based on Zenoss Core 4.2.5 SUP 671
 
title branch added to limit output in report
 
plugin version to provide extensive logging
 
 
reportmail sample included in libexec directory
 
 
|Compatible with=Zenoss Core 3.2.x, Zenoss Core 4.2.x
 
}}{{Release
 
 
|Version=1.2.9
 
|Version=1.2.9
 
|Tag=ae66f07eb01e2fa776c3d1fb664eae93da23d96a
 
|Tag=ae66f07eb01e2fa776c3d1fb664eae93da23d96a
Line 79: Line 62:
 
}}
 
}}
 
}}
 
}}
Some of this functionality is now built-in to the standard product.
+
This functionality is now built-in to the standard product - or at least it will be when the bug is fixed!
 
+
 
{{ZenPackFooter}}
 
{{ZenPackFooter}}

Revision as of 14:51, 19 April 2016

Author(s)
Jane Curry
Current Maintainer(s)
Jane Curry
Organization
Skills 1st
License
GNU General Public License, Version 2, or later
ZenPack name
ZenPacks.community.AvailabilityReportPerCollection
More Information
GitHub page/HomePage
Link to more docs
View Documentation
Git sources (for cloning)
Link



Legacy Binaries: 
Download - version 1.2.4 for Python 2.6
Download - version 1.2.3 for Python 2.6
Download - version 1.2.1 for Python 2.6
Download - version 1.2.6 for Python 2.6
Download - version 1.2 for Python 2.4
Download - version 1.2.6 for Python 2.4
Download - version 1.1 for Python 2.4
Download - version 1.2.5 for Python 2.6

Availability Report Per Collection ZenPack

This ZenPack extends Juerg Gerber's Availability Per Group Report, adding support for additional organizers. You can now specify Group, System, Location and Device Class, in addition to the standard event availability report.

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.2.9- Download
Summary of changes: Device field uses titleOrId
Released on 2012/11/01
Compatible with Zenoss Core 2.5.x, Zenoss Core 3.2.x
Version 1.2.8- Download
Compatible with Zenoss Core 2.5.x, Zenoss Core 3.2.x
Version 1.2.7- Download
Compatible with Zenoss Core 2.5.x, Zenoss Core 3.2.x

Background

This functionality is now built-in to the standard product - or at least it will be when the bug is fixed!

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.community.AvailabilityReportPerCollection-*.egg
  4. Restart these services:
    $ Restart Zenoss.  Subsequent changes, you can probably get away with just bouncing zenhub and zopectl in a Core environment.

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 git://github.com/jcurry/ZenPacks.community.AvailabilityReportPerCollection.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.community.AvailabilityReportPerCollection
  4. Finally, restart these serivices:
    $ Restart Zenoss.  Subsequent changes, you can probably get away with just bouncing zenhub and zopectl in a Core environment.

Discuss

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

blog comments powered by Disqus