Modified items

All recently modified items, latest first.

ZenPacks.turner.CiscoMDS-4.2.5_1.2.2-1.lbn13.noarch: Memory, CPU, power, and temperature performance monitoring of Cisco MDS devices.

ZenPacks.rhybudd.alerts-4.2.5_1.0.0-2.lbn13.noarch: This ZenPack adds new event notification actions that are used by the zenactiond daemon to instantly deliver alerts to any Rhybudd enabled Android devices. Features The following event notification actions have been added: Send Alert to Rhybudd This action allows Zenoss to push events directly to Android devices that have the Rhybudd App installed. Alert delivery is usually sub-second. Rhybudd is free, open source and available from http://bit.ly/ZenossAndroid Limitations These notification actions are not able to provide immediate feedback as to whether or not configuration information is correct, so the zenactiond.log file must be checked to ensure that the actions are working correctly. Rhybudd must be installed to your phone or tablet and the steps detailed in the usage section below must be followed. Usage Phone / Tablet: New Install: Install the Rhybudd app to your phone. Configure the Zenoss server details (URL, username & password) Tap the Configure Rhybudd Push Tab Confirm all tests pass [Optional] Add an event filter (see below for server side configuration of filters) Existing Install upgraded to Rhybudd 4.0 Load up the app Tap the Home / Drawer menu icon Choose Configure Rhybudd Push Confirm all tests pass [Optional] Add an event filter (see below for server side configuration of filters) Zenoss: Basic Configuration: Navigate to Events -> Triggers page. Click on the Notifications menu item. Click on the plus sign ('+') to add a new notification. From the dialog box, specify the name of the notification and select the Send Alert to Rhybudd action. Enable the notification and add a trigger to be associated with this action. Configuring Filters: Follow steps 1 - 4 of Basic Configuration Click on the Contents tab. Input a "Filter Key" Click on the Submit button. On your Android device tap the Home / Drawer menu icon Choose Configure Rhybudd Push Confirm all tests pass Add the Filter key from Step 3 into the edit box. Tap Back or the Home button on the ActionBar Advanced Configuration: To prevent your alerts traversing the ColdStart.io infrastructure and instead have them go straight to your phone (via Google GCM) do the following; Login to Zenoss and navigate to Advanced Select Rhybudd Push from the left hand menu Follow the instructions from Google to create a GCM key http://developer.android.com/google/gcm/gs.html Add the GCM API Key and Sender ID to the page, press submit On your phone load the app, tap the Home icon, choose Configure Rhybudd Push, tap the refresh icon on the action bar. (This will update the local Sender ID and change the GCM Registration ID if neccessary)

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn13.noarch: KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.lbn.SquidMonitor-client-4.2.5_4.0.2-1.lbn13.noarch: Configuration for any server being monitored by SquidMonitor

ZenPacks.lbn.SquidMonitor-4.2.5_4.0.2-1.lbn13.noarch: his ZenPack monitors Squid Proxy server's using SNMP. The following MIB's are monitored: cacheClients 1.3.6.1.4.1.3495.1.3.2.1.15.0 cacheCurrentFileDescrCnt 1.3.6.1.4.1.3495.1.3.1.12.0 cacheCurrentFileDescrMax 1.3.6.1.4.1.3495.1.3.1.13.0 cacheCurrentResFileDescrCnt 1.3.6.1.4.1.3495.1.3.1.11.0 cacheCurrentUnusedFDescrCnt 1.3.6.1.4.1.3495.1.3.1.10.0 cacheDnsSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.8.5 cacheHttpAllSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.2.5 cacheHttpErrors 1.3.6.1.4.1.3495.1.3.2.1.3.0 cacheHttpHitSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.5.5 cacheHttpHits 1.3.6.1.4.1.3495.1.3.2.1.2.0 cacheHttpInKb 1.3.6.1.4.1.3495.1.3.2.1.4.0 cacheHttpMissSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.3.5 cacheHttpNhSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.11.5 cacheHttpNmSvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.4.5 cacheHttpOutKb 1.3.6.1.4.1.3495.1.3.2.1.5.0 cacheIcpQuerySvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.6.5 cacheIcpReplySvcTime.5 1.3.6.1.4.1.3495.1.3.2.2.1.7.5 cacheNumObjCount 1.3.6.1.4.1.3495.1.3.1.7.0 cacheProtoClientHttpRequests 1.3.6.1.4.1.3495.1.3.2.1.1.0' cacheRequestByteRatio.1 1.3.6.1.4.1.3495.1.3.2.2.1.10.1 cacheRequestByteRatio.5 1.3.6.1.4.1.3495.1.3.2.2.1.10.5 cacheRequestByteRatio.60 1.3.6.1.4.1.3495.1.3.2.2.1.10.60 cacheRequestHitRatio.1 1.3.6.1.4.1.3495.1.3.2.2.1.9.1 cacheRequestHitRatio.5 1.3.6.1.4.1.3495.1.3.2.2.1.9.5 cacheRequestHitRatio.60 1.3.6.1.4.1.3495.1.3.2.2.1.9.60 cacheSysPageFaults 1.3.6.1.4.1.3495.1.3.1.1.0 cacheSysStorage 1.3.6.1.4.1.3495.1.1.2.0 cacheSysVMsize 1.3.6.1.4.1.3495.1.1.1.0 cacheUptime 1.3.6.1.4.1.3495.1.1.3.0 A full list of possible MIB's to extend your monitoring is available at http://wiki.squid-cache.org/Features/Snmp To use this zenpack, you'll need to enable snmpd in squid.conf: acl snmppublic snmp_community mysecretcommunity snmp_port 3401 snmp_access allow snmppublic all and proxy these through your hosts snmpd.conf: view systemview included .1.3.6.1.4.1.3495.1 proxy -m /usr/share/snmp/mibs/SQUID-MIB.txt -v2c -Cc -c mysecretcommunity localhost:3401 .1.3.6.1.4.1.3495.1

ZenPacks.lbn.LDAPMonitor-4.2.5_4.0.2-1.lbn13.noarch: LDAPMonitor ----------- LDAPMonitor provides a method for pulling performance metrics from any LDAP server which implements the cn=Monitor standard. The monitor works by directly querying the LDAP server using the configured user dn and password credentials. Make sure that your LDAP server is available from your Zenoss console, you've enabled cn=monitor on it, and that the user has sufficient permissions to perform a 'cn=snmp,cn=monitor' search. The following metrics will be collected and graphed for the LDAP Server: * Operations o Add Entry o Modify Entry o Delete Entry o Search Entry * Bindings o Anonymous o Simple Auth o Unauthorised * Errors o Bind Security o Security o Other Errors o Failures * Response Time * Referrals You can add LDAP monitoring to the device within Zenoss by simply binding the LDAPMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the LDAPMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the LDAP Server metrics from this device.

ZenPacks.lbn.CouchDB-4.2.5_4.0.1-3.lbn13.noarch: CouchDB is a ZenCommand monitor for remotely gathering CouchDB server statistics. The following metrics will be collected and graphed for the LDAP Server: * Database Statistics o Reads o Writes o Open Databases o Open File System Files o Request Time * Daemon Statistics o Bulk Requests o Requests o Temporary View Reads o View Reads * Operations o Copy o Delete o Get o Head o Move o Post o Put * HTTP Statuses (20x, 30x, 4xx, 500) You can add CouchDB monitoring to the device within Zenoss by simply binding the CouchDB template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the CouchDB template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the CouchDB Server metrics from this device.

ZenPacks.lbn.Base-4.2.5_4.0.3-2.lbn13.noarch: Last Bastion Network product information into your Zenoss Server, and all the necessary monkey patches to your Zope environment.

ZenPacks.lbn.AvayaPBX-4.2.5_4.0.0-1.lbn13.noarch

ZenPacks.lbn.Asterisk-client-4.2.5_4.0.1-3.lbn13.noarch: Configuration for any server being monitored by Zenoss/Asterisk

ZenPacks.lbn.Asterisk-4.2.5_4.0.1-3.lbn13.noarch: This ZenPack monitors Asterisk VoIP server's using SNMP. The following MIB's are monitored: Active Calls 1.3.6.1.4.1.22736.1.2.5.0 Agent 1.3.6.1.4.1.22736.1.5.4.1.7.5 Bridge 1.3.6.1.4.1.22736.1.5.4.1.7.1 Calls Processed 1.3.6.1.4.1.22736.1.2.6.0 Current Channels Used 1.3.6.1.4.1.22736.1.5.1.0 IAX2 1.3.6.1.4.1.22736.1.5.4.1.7.4 Local 1.3.6.1.4.1.22736.1.5.4.1.7.10 MGCP 1.3.6.1.4.1.22736.1.5.4.1.7.8 Phone 1.3.6.1.4.1.22736.1.5.4.1.7.3 SIP 1.3.6.1.4.1.22736.1.5.4.1.7.6 USTM 1.3.6.1.4.1.22736.1.5.4.1.7.2 Woomera 1.3.6.1.4.1.22736.1.5.4.1.7.9 A full list of possible MIB's to extend your monitoring is available at http://wiki.squid-cache.org/Features/Snmp To use this zenpack, you'll need to install the asterisk-snmp server on your Asterisk box. You'll also want to either run up Asterisk as root to bind to port 161 as a standalone SNMP daemon (not recommended), or configure AgentX within your snmpd (recommended), using a configuration as follows in /etc/snmp/snmpd.conf: master agentx agentXPerms 0660 0550 nobody asterisk A full list of Asterisk MIB definitions can be found at https://wiki.asterisk.org/wiki/display/AST/Asterisk+MIB+Definitions

ZenPacks.lbn.APCUPS-4.2.5_4.0.1-1.lbn13.noarch: 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.community.puppet-4.2.5_1.21-1.lbn13.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.

ZenPacks.community.libvirt-4.2.5_1.97-1.lbn13.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.f5-4.2.5_1.7-1.lbn13.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.Varnish3-4.2.5_1.2-1.lbn13.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.SuSE-4.2.5_1.1-1.lbn13.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.Splunk-4.2.5_1.1.1-2.lbn13.noarch: This ZenPack allows Splunk alerts to be sent to Zenoss as alerts; escalation can then be handled with Zenoss alerts.

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.

« Previous 20 items Next 20 items » 1 ... 2331 2332 2333 2334 2335 2336 2337 ... 2448


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

Sections

Modified items