Search results for zenoss

Products.Zuul-5.0.5-3.lbn19.noarch

Zenoss Zuul module

ZenPacks.AndreaConsadori.Asterisk16-5.0.5_3.0-2.lbn19.noarch

This Monitoring ZenPack provides SNMP-based monitoring for Asterisk 1.6

ZenPacks.Nova.Cisco.Mibs-5.0.5_1.1-2.lbn19.noarch

This ZenPack consists of all the publicly available (and edited to be loadable into Zenoss) MIBs for Cisco devices. The MIBs may be used for translating SNMP traps.

ZenPacks.PlixerInternational.Scrutinizer-5.0.5_1.2-2.lbn19.noarch

The Scrutinizer ZenPack provides direct integration between Zenoss and Scrutinizer. This integration allows network engineers to quickly switch between viewing the event details in Zenoss and the detailed network traffic analysis view in Scrutinizer. Network engineers need to quickly find and resolve network performance bottlenecks before they impact customers and end-users. One of the most effective ways to diagnose network performance problems is by analyzing NetFlow data.

ZenPacks.atelepin.cbCiscoQOS-5.0.5_1.2-1.lbn19.noarch

Background ========== This project is a Zenoss extension (ZenPack) primarily intended for ISPs which extensively use different QoS on their network (like MPLS), and need to know statistics by each class. About Cisco Base QOS on Cisco site This is prerelease but all main functionality work. Almost think i need change or add write in the code as TODO or FIXME Overview ======== Because ServicePolicy bound to Interface (IpInterface), installation create additional relation between cbServicePolicy and IpInterface. ZenPack contain automated modeler which grab QOS Object configuration from device. From this configuration modeler create particular class instance and create hierarchy of that objects (see more about nested object in cisco site). In this release i collect only two statistic item PostPolicyBitRate and PostPolicyDropRate. From code point of view each statistic item is different component, but from user point of view, this item belong to cbServicePolicy and statistics should be visible as single item (for example on single graph). In this case cbServicePolicy work not only as container but also provide internal API to gather statistic from his child.

ZenPacks.community.ConstructionKit-5.0.5_2.5-1.lbn19.noarch

This ZenPacks automates to a large extent the development of other ZenPacks. It eliminates the bulk of "boilerplate" code that accompanies the typical "custom component" type of zenpack while providing many nice features. The goal is to reduce the maintenance cost (development time) associated with dependent ZenPacks by removing most of their code. ConstructionKit-dependent ZenPacks should consist only of a Definition.py class file that subclasses the provided "BasicDefinition" class, as well as any additional ZenPack-specific files such as modeler plugins, check scripts, and exported Zenoss templates, event classes, etc (objects.xml).

ZenPacks.community.DistributedCollectors-5.0.5_2.0.1-1.lbn19.noarch

Description: This ZenPack provides UI for configuring multiple collectors with Zenoss Core. It implement remote collector configuration method described in How to install distributed collectors manual (http://community.zenoss.org/docs/DOC-2496). Adding Remote Collector 1. install DistributedCollectors ZenPack on master server 2. install Zenoss on remote collector without any ZenPacks 3. configure "ssh public key authentication" on remote collector for user 'zenoss' 4. in "Collectors" -> select menu item "Add Remote Monitor..." and enter name or ip address of remote collector Updating Remote Collectors (after zenpacks install or remove) 1. in "Collectors" select all remote collectors you want update. 2. in "Collectors" -> select menu item "Update Remote Monitors..."

ZenPacks.community.OpenTSDB-5.0.5_1.0.0-1.lbn19.noarch

Publish Zenoss RRD data to OpenTSDB

ZenPacks.community.PagerDuty-5.0.5_1.0.0-2.lbn19.noarch

DESCRIPTION: This ZenPack is designed to facilitate a tight integration between Zenoss (www.zenoss.com) and Pagerduty (www.pagerduty.com). It provides the following capabilities: 1. A script designed to be run by Zenoss "Event Commands" (3.x) or "Notifications" (4.x) that creates Pagerduty incidents for specific Zenoss events. a. incident is created for Pagerduty service by specifying the service key as a runtime argument. b. if Pagerduty service is in maintenance, the Zenoss event will be acknowledged and updated with a relevant message c. if Pagerduty service is disabled, the Zenoss event will be left unacknowledged, but updated with a relevant message 2. A Zenoss daemon that runs periodically and synchronizes Zenoss event/Pagerduty incidents. The daemon: a. determines which side (Zenoss or Pagerduty) was most recently updated. b. changes the status of the non-authoritative event/incident to match the authoritative one c. copies/formats Pagerduty incident logs for view within the Zenoss event console details. This ZenPack uses the web service APIs of both Zenoss and PagerDuty. CREATING PAGERDUTY INCIDENTS: Since Pagerduty uses a key to identify the "Services" that notifications should be assigned to, the idea is to create a default service key event attribute (via transform) that Zenoss will use when creating Pagerduty Incidents. The default service key can then be overwritten by other event transforms according to the administrator's needs. For example, the following event transform might be applied at the root of the event class hierarchy. This transform determines whether a given device is a Windows or Unix device, and assigns the appropriate service key accordingly: unixServiceKey = 'UNIXKEY' # Unix Team windowsServiceKey = 'WINDOWSKEY' # Windows Team defaultServiceKey = 'DEFAULTKEY' # Default Team try: devClass = device.deviceClass().getOrganizerName() # string representing device class organizer if 'Linux' in devClass: evt.pdServiceKey = unixServiceKey elif 'AIX' in devClass: evt.pdServiceKey = unixServiceKey elif 'WMI' in devClass: evt.pdServiceKey = windowsServiceKey elif 'Windows' in devClass: evt.pdServiceKey = windowsServiceKey else: evt.pdServiceKey = device.zPDServiceKey except: # set to default if nothing found evt.pdServiceKey = defaultServiceKey This initial transform can then be overridden later by other event transforms depending on the event class (or whatever the administrator designs). Once the event has a corresponsing service key assigned, it can be passed as a parameter to an "Event Command" (Zenoss 3.x) or "Notification" (Zenoss 4.x) such as: python zenpagerduty.py -a create -z ${dev/zPDZenossServer} -u ${dev/zPDZenossUser} -p ${dev/zPDZenossPass} -H ${dev/zPDDomain} -T ${dev/zPDToken} -U ${dev/zPDUser} -e ${evt/evid} -S ${evt/pdServiceKey} which creates the Pagerduty Incident with the provided arguments. SYNCHRONIZING SERVICE: This ZenPack provides a service daemon called "zenpdsync" which periodically (default 60 seconds) pulls the last N ('eventsBuffer' option default 20) events from both Zenoss and Pagerduty. It correlates these into pairs and determines which was last updated. If the status of one of the pair differs from the other, then the most recently updated one's status is copied to the other. Relevant Pagerduty incident log details are also copied to the Zenoss console. ZPROPERTIES PROVIDED: zPDZenossServer: hostname of zenoss server zPDZenossUser: zenoss user allowed to query events zPDZenossPass: password for zenoss user zPDDomain: YOURNAMEHERE.pagerduty.com zPDToken: Token key needed for API calls zPDUser: Pagerduty user used for automatic updates (this will show in the console, I use a fake user called "Zenoss") zPDServiceKey: optional per-device service key (would need to be assigned in transform if used, however) COMPONENTS: The ZenPack has the following objects: An example notification (Zenoss 4.x) An example event command (Zenoss 3.x) INSTALLATION: It is recommended to run the "zenpdsync" from only one hub or collector, since the process does not need to be run multiple times for a single Zenoss installation. This means disabling the "zenpdsync" daemon on all but one of the hub/collectors. Be sure also to set defaults for the zProperties, as well as creating an event transform under the root class similar to the sample above. The bare minimum event transform would be: try: evt.pdServiceKey = device.zPDServiceKey except: evt.pdServiceKey = 'YOURSERVICEKEY' A transform has not been provided, as the author has encountered complications in the past related to event classes (they get removed if the Zenpack is uninstalled).

ZenPacks.community.ResponsiveUI-5.0.5_2.0.5-1.lbn19.noarch

Make life of mobile Zenoss users a bit easier by adding light user interface to access Infrastructure, Device details, Components and Events console. ZenPack also extends Zenoss with settings for User Interface colors and full-screen mode. Mobile User Interface When accessing Zenoss from your mobile device (phone, tablet) it will show lite pages for: Login page Add a Single Device Infrastructure Events console Device overview Device components Device events This can be turn ON/OFF on User Interface settings page in Zenoss. Tune Zenoss colors for your own Zenpack brings a color settings to Zenoss: navigation bar menu sidebar panel table rows Zen mode ON A small button in the footer to hide sidebar and navigation. Cool for small screens.