Search results

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.

ZenPacks.community.SQLDataSource-5.0.5_1.99-2.lbn19.noarch

This Functionality ZenPack provides a new zenperfsql daemon and SQL data source. It based on Twisted twisted.enterprise.adbapi interface to the standardized DB-API 2.0 API, which allows you to access a number of different RDBMSes.

ZenPacks.community.Splunk-5.0.5_1.1.1-2.lbn19.noarch

This ZenPack allows Splunk alerts to be sent to Zenoss as alerts; escalation can then be handled with Zenoss alerts.

ZenPacks.community.SuSE-5.0.5_1.1-1.lbn19.noarch

This SSH-based ZenPack extends the Linux Monitor and Linux Monitor AddOn ZenPacks to provide additional functionality for SuSE Linux, specifically OS Make and Software inventory.

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

DESCRIPTION: This ZenPack allows Zenoss to monitor VMware ESXi Hosts and VMs via the vSphere SDK for Perl. It creates the /Server/VMware/ESXi Device Class. All ESXi Hosts have to be added to this Device Class. INSTALLATION: First install the vSphere SDK for Perl on your Zenoss Collector Server. After that you can install the ZenPack as usually and restart Zenoss. ZPROPERTIES: The ZenPack will add two zProperties: zVSphereUsername: Name of a User that has read-only access to the ESXi Host zVSpherePassword: The corresponding Password

ZenPacks.community.Varnish3-5.0.5_1.2-1.lbn19.noarch

A ZenPack to provide support for Varnish version 3.x metrics. It introduces a new command parser that is intended to be run over SSH. Metrics are parsed from the output of the varnishstat command on the Varnish 3.x server

ZenPacks.community.f5-5.0.5_1.7-1.lbn19.noarch

The ZenPack has the following: /Network/f5 Device Class A Device template which graphs many of the same performance stats as would be seen in the Overview >> Performance section of the 10.x UI Virtual Server Component Modeling A component template for virtual servers. Virtual Server filtering. This pack adds a new zProperty, zF5BigipVirtualServerNameFilter, which when set will limit which virtual servers are included during a modeling cycle. Node Component Modeling A component template for nodes. Node filtering. This pack adds a new zProperty, zF5BigipNodesNameFilter, which when set will limit which nodes are included during a modeling cycle. Pool Component Modeling A component template for Pools. Pool filtering. This pack adds a new zProperty, zF5BigipPoolsNameFilter, which when set will limit which pools are included during a modeling cycle.

ZenPacks.community.libvirt-5.0.5_1.97-1.lbn19.noarch

This ZenPack leverages the libvirt API for monitoring virtualization servers (e.g. XEN, KVM, etc...). This uses the system python and libvirt python API to monitor various virtualization platforms remotely. It provides a /Server/libvirtHost device class and this module is tested using ssh as a transport for the libvirt API, it could be made to use TLS or TCP with further development. It provides a libvirtvirtualHostlist report as well. You can set zLibvirtUsername and zLibvirtConnectType to customize access to the hosts, though only qemu+ssh:// was tested at the moment. libvirt supports: * The Xen hypervisor on Linux and Solaris hosts. * The QEMU emulator * The KVM Linux hypervisor * The LXC Linux container system * The OpenVZ Linux container system * The User Mode Linux paravirtualized kernel * The VirtualBox hypervisor * The VMware ESX and GSX hypervisors * Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems

ZenPacks.community.mib_utils-5.0.5_1.08-1.lbn19.noarch

Once you navigate to the Mibs tree (ie /zport/dmd/Mibs) you'll be able to access some new menu items: Download MIB... This item allows you to copy-n-paste URLs from different vendor's MIB files, such as http and ftp URLs. This option can understand tar files, zip files and plain MIBs, and will import them and show the results of the import in a new window. Install MIB... Named the same as the "Install ZenPack..." menu item, this will allow you to upload a MIB (in tar, zip or plain MIB format) to the Zenoss server. Once the MIB has been uploaded to the server, this option also shows the results of the import in a new window. Once a MIB has been loaded, you can start to see the difference between having the ZenPack and not having the ZenPack. Little magnifying glass icons appear in front of every MIB file, and if you click the magnifying glass it brings up a tree-based browser (ie one that understands the OID hierarchy, so that the OID x.2 follows x.1, not x.11). (It also loads a popup, so if you don't allow popups from your Zenoss server, you'll need to enable them, close down the new windows and try it again. A popup window is used so that you can expand the tree window to be as large as you like and still be able to view the contents of the OID.) The MIB browser is split up into three sections: * A menu bar showing when the MIB was last loaded * A set of tabs which will allow you to set different options. * A MIB tree, which has two roots: Nodes and Traps The menu bar shows the last time that the MIB was loaded from the Zenoss server. Menu items can be attached through the regular Zenoss method of using the Settings -> Menus tab. When using the Settings -> Menus tab, the menu key for the MIB Browser is "MIB_info". There are currently four tabs available: * Info: where information about the MIB can be changed, such as the MIB specification language, the description and the contact. * Lookup: where you can lookup information about an OID using either its name or its numeric form. After you hit return or change the focus on the window the results will be displayed on the screen. (NB: snmptranslate must be in the zenoss user's path for this to work.) * Test settings: Enter the SNMP version 1 information into this tab and then when you right click on a node or trap you can query this device starting at that OID. * Hide Tabs: Sometimes the screen real estate is important, so this provides a way to reclaim that space. The MIB browser shows you the description and other information about the MIB, and there are two trees which you can select from the MIB: Nodes and Traps. Any information not in the MIB (ie traps) will make part of the tree stop at the root (ie Nodes or Traps). You can expand or contract any portion of the tree that you wish, and the information about any node that you select will appear in the OID popup window. If you hover over a node, the truncated description of the OID will appear in the tooltip. By right-clicking on a Node or a Trap, you can select a menu item to bring up a new pop-up window which will run a SNMP version 1 snmpwalk on the defined test device and display the output starting from the OID that you've hovered over. Other details: Two extra routines are provided to make exploring Zenoss in XML a little easier: showXML and showMibasXML. showXML: This can be tacked on to the end of almost anywhere in the /zport hierarchy and it will show you what the XML will look like if the data were to be exported to disk. This tool allows you to gain a better intuitive understanding of how the Zenoss XML files will actually appear. The output is XML, so it relies on your browser's native XML-handling capability to show you the XML tree and allow you to navigate that tree. showMibasXML: This is like showXML, except that it only works from inside of the /zport/dmd/Mibs/mibs hierarchy, and it outputs the XML file in a similar format to what smidump produces. (smidump is the tool Zenoss uses to turn MIB files into Python code, which is then introduced into the Zope database.) Additionally, the XML tree of nodes and traps is produced sorted by OID. For reference, a much smaller and easier to code version that doesn't sort by OID (which is required for the browser) is included in the skins directory of the ZenPack.

ZenPacks.community.puppet-5.0.5_1.21-1.lbn19.noarch

This ZenPack provides support for the following in Puppet (via ssh) Report and listing of puppet clients for each master on a separate tab Report of all puppet clients in a PuppetClientList report Tracking of update times of clients Device addition from puppet via events The ZenPack provides a device class /Server/PuppetMaster, with a collector plugin PuppetModeler.