Search results for zenoss

ZenPacks.community.mib_utils-4.2.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.lbn.Asterisk-4.2.5_4.0.1-3.lbn19.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.Base-4.2.5_4.0.3-3.lbn19.noarch

Last Bastion Network product information into your Zenoss Server, and all the necessary monkey patches to your Zope environment.

ZenPacks.lbn.CouchDB-4.2.5_4.0.1-3.lbn19.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.LDAPMonitor-4.2.5_4.0.2-2.lbn19.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 have 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.SquidMonitor-4.2.5_4.0.2-1.lbn19.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.ZopeMonitor-4.2.5_4.0.4-3.lbn19.noarch

ZopeMonitor ------------- ZopeMonitor provides a method for pulling performance metrics from a Zope Application Server (http://www.zope.org/) directly into Zenoss. It is necessary to first install the munin.zope eggs from pypi.python.org or our own repo at http://linux.last-bastion.net/LBN/up2date/monitor, and to have wget installed on this server. The monitor works by utilising ZenCommand to run wget on the local system - you do not need to make zope ports available through your firewall. The munin plugins do require a user with 'View Management Screens' access at the root however. This is configured using the zZopeURI zProperty of the device. This parameter uses Extended HTTP Authentication to specify user credentials, host and port. Note that the host is the hostname on the remote instance and should probably remain 'localhost' unless you've explicitly bound your Zope to a NIC. Note that the munin plugins expect to be installed on a Unix-like operating system with a /proc filesystem. The following metrics will be collected and graphed for the Zope Server. * Threads (only if you set up munin.zope on target - see code) o Free threads o Total threads * Cache o Total objects o Total objects in memory o Targe number * ZODB Activity o Total connections o Total load count o Total store count * Memory Utilisation o VmHWM - peak resident set size ("high water mark") o VmExe - size of text segments o VmStk - size of stack segments o VmPeak - peak virtual memory size o VmData - size of data segments o VmLck - locked memory size o VmPTE - page table entries size o VmLib - shared library code size o VmRSS - resident set size Once your Zope Server has the munin plugins installed, you can add Zope monitoring to the device within Zenoss by simply binding the ZopeMonitor 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 ZopeMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Zope Server metrics from this device.

ZenPacks.oie.KannelMonitor-4.2.5_3.0.0-3.lbn19.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.rhybudd.alerts-4.2.5_1.0.0-2.lbn19.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)