Modified items

All recently modified items, latest first.

ZenPacks.community.SQLDataSource-4.2.5_1.99-2.lbn13.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.RDBMS-4.2.5_2.5-1.lbn13.noarch: This ZenPack provides basic "Database" and "DBSrvInst" component class.

ZenPacks.community.OracleMon-4.2.5_1.2-1.lbn13.noarch: This Monitoring ZenPack provides Oracle Database monitoring. There is a community.sql.OracleDatabaseMap zCollectorPlugin that the device will need to use.

ZenPacks.community.LinuxMonitorAddOn-4.2.5_1.0-1.lbn13.noarch: This SSH-based ZenPack supplements the Linux Monitor ZenPack and provides perf monitoring for Interfaces and adds routing and memory as well.

ZenPacks.community.HPUXMonitor-4.2.5_2.2-2.lbn13.noarch: HPUX SNMP-based monitoring/coordination

ZenPacks.community.Fortigate-4.2.4_1.2.1-1.lbn13.noarch: Provides a /Network/Router/Firewall/Fortigate Device Class and a Fortigate template that can be \ bound to monitor CPU usage, Memory Utilization and Number of Sessions for a Fortigate Firewall.

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

ZenPacks.chudler.GoogleAppEngine-4.2.5_1.0-1.lbn13.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.lbn13.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.lbn13.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.lbn13.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.lbn13.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.4_1.2-1.lbn13.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.Nova.Cisco.Mibs-4.2.5_1.1-1.lbn13.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-1.lbn13.noarch: SNMP-based modeling and monitoring for Catalyst Switch devices running CatOS

ZenPacks.Firestar.CiscoASA-4.2.5_2.1.2-1.lbn13.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.

SOAPpy-0.11.6-10.fc12.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.

PyXML-0.8.4-28.fc18.1302260759kf.armv6hl: An XML package for Python. The distribution contains a validating XML parser, an implementation of the SAX and DOM programming interfaces and an interface to the Expat parser.

PyXML-0.8.4-27.lbn13.x86_64: An XML package for Python. The distribution contains a validating XML parser, an implementation of the SAX and DOM programming interfaces and an interface to the Expat parser.


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