Modified items

All recently modified items, latest first.

ZenPacks.community.ConstructionKit-4.2.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.CiscoEnvMon-4.2.5_1.1-1.lbn19.noarch: Cisco Environmental monitoring including fans, temperature sensors, power supplies and expansion modules.

ZenPacks.chudler.GoogleAppEngine-4.2.5_1.0-1.lbn19.noarch: With this ZenPack you can monitor the status of your Google AppEngine applications. It provides: All Quota statistics (allowances, percent used, and raw used). Application status (version deployed) Monitoring of multiple google accounts Automatic detection of new quotas types Automatic detection of new applications and changes to existing applications

ZenPacks.atelepin.cbCiscoQOS-4.2.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.ZenSystems.ApcUps-4.2.4_1.2-6.lbn19.noarch: The ZenPack has the following Device Class /Devices/Server/Windows Components are: ApcUpsBattery which has details for: Various elements of battery status Modeler plugins are: ApcUpsDeviceMap Gathers Hardware and Software manufacturer and product Serial number Total number of battery packs Number of bad battery packs Basic output status ApcUpsBatteryMap Gathers battery data for status Time on battery Battery last replacement date Battery replacement indicator Device template ApcUps provides device-level performance information: Data Sources Voltage Current Remaining capacity and time Temperature Thresholds Low capacity Low time remaining High temperature Graph Definitions Voltage Current Remaining capacity Remaining time Temperature Device template ApcUpsInsAndOuts provides specific input / output performance information: Data Sources Input frequency and voltage Output frequency, voltage, load and current Thresholds High load Graph Definitions Input frequency and voltage Output frequency, voltage, load and current A separate APC UPS Information menu delivers tabular and graphical information for the overall device

ZenPacks.TwoNMS.PrinterMIB-4.2.5_2.0.0-2.lbn19.noarch: This ZenPack monitors printers supporting the new RFC3805 PrinterMIB (supersedes RFC1759). Version 2.0.0 creates separate components for toners, supplies and input trays. In case you don't see the Printer components then try deleting the printer + adding it directly to the /Printer/PrinterMIB tree.

ZenPacks.RomanTykhonov.OracleDB-4.2.5_2.0-2.lbn19.noarch: With SNMP Trap destination setup in Oracle Enterprise Manager it is the best way to monitor many Oracle Single Instance/RACs for FREE. (if you have Oracle Standard Edition - Perfomance Tab have to be disabled due to Standard Edition Licence Agreement)

ZenPacks.PlixerInternational.Scrutinizer-4.2.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.PlixerInternational-4.2.5_1.2-2.lbn19.noarch: ZenPacks.PlixerInternational.Scrutinizer module

ZenPacks.Nova.Cisco.Mibs-4.2.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.Nova.Cisco.Catalyst-4.2.5_1.0-2.lbn19.noarch: he Cisco Catalyst ZenPack provides SNMP-based modeling and monitoring for Catalyst Switch devices running CatOS. It consists of a modeler plugin called 'zenoss.snmp.InterfaceCatOsMap', which works in conjunction with 'zenoss.snmp.InterfaceMap' to properly map interfaces on Catalyst switches running CatOS. It also comes with a performance template for monitoring CPU and Memory on Catalyst switches running CatOS.

ZenPacks.Nova.Cisco-4.2.5_1.0-2.lbn19.noarch: ZenPacks.Nova.Cisco.Catalyst module

ZenPacks.Firestar.CiscoASA-4.2.5_2.1.2-2.lbn19.noarch: This ZenPack is for Cisco Adaptive Security Appliance (ASA), and provides CPU utilization, free memory available, active VPN tunnels, RAS sessions, and IKE dropped packets. It also includes all the necessary MIB configurations to handle incoming SNMP trap events from these appliances.

ZenPacks.Firestar-4.2.5_2.1.2-2.lbn19.noarch: ZenPacks.Firestar.CiscoASA module

SOAPpy-0.11.6-16.fc19.noarch: The goal of the SOAPpy team is to provide a full-featured SOAP library for Python that is very simple to use and that fully supports dynamic interaction between clients and servers.


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.