Modified items

All recently modified items, latest first.

ZenPacks.zenoss.OpenStack-4.2.5_1.2.3dev-2.lbn19.noarch: This project is a Zenoss extension (ZenPack) that allows for monitoring of OpenStack. This means that you can monitor the flavors, images and servers a user or consumer perspective. OpenStack Compute v1.1 (Cactus) is known to be supported. Specifically this means that Rackspace's CloudServers can be monitored. In the future it is likely that support for monitoring OpenStack Storage (Swift) will be added. OpenStack is a global collaboration of developers and cloud computing technologists producing the ubiquitous open source cloud computing platform for public and private clouds. The project aims to deliver solutions for all types of clouds by being simple to implement, massively scalable, and feature rich. The technology consists of a series of interrelated projects delivering various components for a cloud infrastructure solution. Once the OpenStack ZenPack is installed you can begin monitoring by going to the infrastructure screen and clicking the normal button for adding devices. You'll find a new option labeled, "Add OpenStack." Choose that option and you'll be presented with a dialog asking for the following inputs. 1. Username - Same username used to login to OpenStack web interface 2. API Key - Can be found by going to "Your Account/API Access" 3. Project ID - This can be left blank if you don't know what it is 4. Auth URL - For Rackspace this would be https://auth.api.rackspacecloud.com/v1.0 5. Region Name - This can be left blank if you don't know what it is Once you click Add, Zenoss will contact the OpenStack API and discover servers, images and flavors. Once it is complete you'll find a new device in the OpenStack device class with the same name as the hostname or IP you entered into the dialog. Click into this new device to see everything that was discovered. The following types of elements are discovered. * Servers * Images * Flavors The following metrics are collected. * Total Servers and Servers by State o States: Active, Build, Rebuild, Suspended, Queue Resize, Prep Resize, Resize, Verify Resize, Password, Rescue, Reboot, Hard Reboot, Delete IP, Unknown, Other * Total Images and Images by State o States: Active, Saving, Preparing, Queued, Failed, Unknown, Other * Total Flavors Status monitoring is performed on servers and images with the following mapping of state to Zenoss event severity. Servers State to Severity Mapping: * Reboot, Hard Reboot, Build, Rebuild, Rescue, Unknown == Critical * Resize == Error * Prep Resize, Delete IP == Warning * Suspended, Queue Resize, Verify Resize, Password == Info * Active == Clear Images State to Severity Mapping: * Failed, Unknown == Critical * Queued, Saving, Preparing == Info * Active == Clear If you are also using Zenoss to monitor the guest operating system running within the server Zenoss will present the graphs for that operating system when the graphs option is chosen for the OpenStack server.

ZenPacks.zenoss.NtpMonitor-4.2.5_2.2.0-1.lbn19.noarch

ZenPacks.zenoss.NNTPMonitor-4.2.5_1.1.0-1.lbn19.noarch

ZenPacks.zenoss.MySqlMonitor-4.2.5_3.0.4dev-3.lbn19.noarch: MySqlMonitor provides a method for pulling performance metrics from the MySQL database server (http://www.mysql.com/) directly into Zenoss without requiring the use of an agent. This is accomplished by utilizing the MySQL client library to connect to the database remotely. The following metrics will be collected and graphed for MySQL server. * Command Statistics (SELECT, INSERT, UPDATE, DELETE) * Select Statistics (Scan, Range Check, Range Join, Full Join) * Handler Statistics (Keyed & Unkeyed Reads, Writes, Updates, Deletes) * Network Traffic (Received & Sent)

ZenPacks.zenoss.Microsoft.Windows-4.2.5_2.2.0-2.lbn19.noarch: This ZenPack provides support for monitoring Microsoft Windows. Monitoring is performed using the Windows Remote Management (WinRM) and Windows Remote Shell (WinRS) to collect Windows Management Instrumentation (WMI) and perfmon data.

ZenPacks.zenoss.Microsoft-4.2.5_2.2.0-2.lbn19.noarch: ZenPacks.zenoss.Microsoft.Windows module

ZenPacks.zenoss.Memcached-4.2.5_1.0.0-1.lbn19.noarch: This ZenPack allows for monitoring of memcached. See the Usage section for details on what is monitored. This ZenPack previously existed as a commercial-only extension to Zenoss called ZenPacks.zenoss.MemcachedMonitor. Upon being released as open source its name was changed to better match today's standards. There already exists a very good community ZenPack for memcached by braudel. As far as I can see there is no compelling reason to use this version over that. Ultimately I'd like to see the ZenPacks come together to reduce confusion. At the time that this ZenPack was originally written, the community version didn't exist.

ZenPacks.zenoss.MSSQLServer-4.2.5_2.0.3-1.lbn19.noarch: MS SQL Server

ZenPacks.zenoss.MSMQMonitor-4.2.5_1.2.1-1.lbn19.noarch: MS Message Queue

ZenPacks.zenoss.MSExchange-4.2.5_2.0.4-1.lbn19.noarch: MS Exchange Monitoring

ZenPacks.zenoss.LinuxMonitor-4.2.5_1.2.1-1.lbn19.noarch: This ZenPack provides RRD templates and command parsers for monitoring Linux hosts.

ZenPacks.zenoss.Layer2-5.0.5_1.1.0dev-1.lbn19.noarch: Features The features added by this ZenPack can be summarized as follows. They are each detailed further below. Discovery and periodic remodeling of Neighbor Switches using CDP/LLDP. Monitoring of MAC Address table or Forwarding Table for each network interface of device. Event suppression based on MAC Address table. Discovery CDP/LLDP based collector plugin zenoss.snmp.CDPLLDPDiscover performs discovery of switches located nearby a selected device. Monitoring The ZenPack binds Layer2Info monitoring templates to the /Network device class in Zenoss. This activates monitoring of Layer 2 MAC forwarding tables for devices under that class. On the detail view of Interfaces components, the Clients MAC addresses subpanel is added with a list of MAC addresses. Those addresses are grouped by the client device they belong to. Event suppression When an upstream switch goes down, a flood of Device is DOWN! events for every device in an affected subnet can be generated. This ZenPack adds a zenevent plugin which suppresses such subsequent events for leaf devices. As a result, a system administator receives only a primary, core error event.

ZenPacks.zenoss.LDAPMonitor-4.2.5_1.4.0-1.lbn19.noarch: ZenPacks.zenoss.LDAPMonitor monitors the response time of an LDAP server (in milliseconds).

ZenPacks.zenoss.JabberMonitor-4.2.5_1.1.0-1.lbn19.noarch

ZenPacks.zenoss.JMXNotificationListener-4.2.5_0.9.1-5.lbn19.noarch: Usage To collect JMX notifications you must edit $ZENHOME/etc/zenjmxnotificationlistener.conf. This file must be used to specify which JMX agents to connect to, and what notifications to collect. After modifying this file you must run ``zenjmxnotificationlistener restart`` for the changes to be affected. Upon installing the ZenPack a default ``zenjmxnotificationlistener.conf`` will be created with the following contents. monitorName=localhost heartbeatInterval=60 heartbeatTimeout=75 connectionRetryInterval=10 xmlRpcUrl=http://localhost:8081/zport/dmd/ZenEventManager xmlRpcUsername=admin xmlRpcPassword=zenoss serverList=LOCALHOST server.LOCALHOST.zenossDevice=localhost server.LOCALHOST.url=service:jmx:rmi:///jndi/rmi://localhost:54107/jmxrmi The scope and attributeFilters properties are optional, and can be used to restrict the notifications captured from a given server. MBeanServerNotification type notifications are ignored by default as they are noisy and unlikely to be useful.

ZenPacks.zenoss.IRCDMonitor-4.2.5_1.1.0-1.lbn19.noarch

ZenPacks.zenoss.IISMonitor-4.2.5_2.0.2-1.lbn19.noarch: IISMonitor collects key metrics from Microsoft IIS. The metrics are collected using Windows Perfmon and require no agent to be installed on the IIS server. The following metrics will be collected and graphed for Microsoft IIS. * Connections Attempts * Throughput (Bytes & Files) * Requests (GET, HEAD, POST, CGI, ISAPI) Standard: GET, HEAD, POST, CGI, ISAPI WebDAV: PUT, COPY, MOVE, DELETE, OPTIONS, PROPFIND, PROPPATCH, MKCOL Other: SEARCH, TRACE, LOCK, UNLOCK Follow these steps to setup your IIS server to have this information collected. 1. Verify that your Zenoss Windows service account has access to the IIS server. Within Zenoss this is specified using zWinUser and zWinPassword. 2. Bind the IIS performance template to the IIS server device within Zenoss.

ZenPacks.zenoss.HttpMonitor-4.2.5_2.1.0-1.lbn19.noarch: ZenPacks.zenoss.HttpMonitor monitors connection response time to an HTTP server and determines whether specific content exists on a Web page.

ZenPacks.zenoss.HPMonitor-4.2.5_2.1.0-1.lbn19.noarch: HPMonitor provides custom modeling of devices running the HP/Compaq Insight Management Agents. It also contains hardware identification for HP proprietary hardware. The information is collected through the SNMP interface. The following information is modeled. * Hardware Model * Hardware Serial Number * Operating System * CPU Information (socket, speed, cache)

ZenPacks.zenoss.HBase-4.2.5_1.0.0-5.lbn19.noarch: Features The features added by this ZenPack can be summarized as follows. They are each detailed further below. Discovery and periodic remodeling of relevant components. Performance monitoring. Event monitoring. Optional service impact with addition of Zenoss Service Dynamics product. Discovery The following components will be automatically discovered through zProperties you provide: Region Servers Attributes: Name (DomainName:port), Start Code, Handler Count, Memstore Upper Limit, Memstore Lower Limit, Log Flush Interval Collections: Regions Regions Attributes: Table, Start Key, Region ID, Region Server, Memstore Flush Size, Max File Size Tables Attributes: Name, Number of Column Families, Column Family Block Size, Compaction, Enabled Performance Monitoring The following metrics will be collected and graphed every 5 minutes by default: HBase Cluster Metrics Region Server Statistics: The number of dead, live and overall number of Region Servers Performance: Average load, Requests Region Servers Region Statistics: Number of Regions, Storefiles and Stores Memory Usage: Max and Used Heap Memory Size (MB) Storage Statistics: Memstore Size (MB), Storefile Index Size (MB), Storefile Size (MB) Requests: Read, Write, Requests/sec Blocks: Block Cache Count, Block Cache Evicted Count, Block Cache Hit Ratio (%), Block Cache Hit Caching Ratio (%) Performance metrics: Compaction Queue Length, Flush Queue Length, Call Queue Length Regions Storage Statistics: Memstore Size (MB), Storefile Index Size (MB), Storefile Size (MB), Storefiles, Stores Requests: Read, Write Event monitoring The following events will be triggered with respect to the monitored metrics: HBase Cluster Error: Connection refused/Credentials not valid. Critical: The percentage of dead servers exceeds 50%. Warning: The percentage of dead servers exceeds 10%. Region Servers Error: Connection refused/Credentials not valid. Error: The server is dead. Warning: The Memstore Size is nearing or exceeding its global.memstore.size (defaults to 40% of maxHeapSize). Info: One or more region servers have been added/removed. Regions Error: Connection refused/Credentials not valid. Warning: The Memstore Size is nearing or exceeding its flush size (128MB by default). Warning: The Storefile Size is nearing or exceeding the recommended maximum size (10GB by default). Tables Info: New table is added. Error: Connection refused/Credentials not valid. Error: The table is disabled or dropped. Service Impact When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for HBase. The following service impact relationships are automatically added. These will be included in any services containing one or more of the explicitly mentioned entities. Service Impact Relationships Region failure affects related Table. Region Server failure affects related Regions. Region servers are affected by HBase hosting device failure. External Impact Relationships Region servers are affected by hosting Hadoop Data Node failure. To add HBase as service to be monitored, add a Dynamic Service Organizer for the service and then add a Dynamic Service to it. Select the new Dynamic Service from the Dynamic Service tree on the left pane and then add the table(s) supporting your HBase service and add them. The Service Dependency tree will be created automatically for your HBase Service. Usage Use the following steps to start monitoring HBase: Select Infrastructure from the navigation bar. Click the device name in the device list. The device overview page appears. Select Configuration Properties from the left panel. Set zHBasePassword, zHBaseUsername and select https for zHBaseScheme if you have Basic access authentication configured on your HBase master (otherwise leave zHBasePassword and zHBaseUsername blank). Set the zHBaseRestPort, zHBaseMasterPort and zHBaseRegionServerPort zProperties, if the values for those ports differ from the default ones. Navigate to the Modeler plugins page of the device containing your HBase server, add the HBaseCollector and HBaseTableCollector modeler plugins. Select Model device from the gear menu.

« Previous 20 items Next 20 items » 1 ... 1879 1880 1881 1882 1883 1884 1885 ... 2449


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

Sections

Modified items