Search results

ZenPacks.zenoss.EsxTop-4.2.5_1.1.1-1.lbn25.noarch

The VMWare ESX Server ZenPack for Core allows you to monitor ESX hosts and guests via VMWares EsxTop utility. The ZenPack uses the resxtop command to gather performance information about VMware Infrastructure ESX servers.

ZenPacks.zenoss.EsxTop-4.2.5_1.1.1-1.lbn25.noarch

The VMWare ESX Server ZenPack for Core allows you to monitor ESX hosts and guests via VMWares EsxTop utility. The ZenPack uses the resxtop command to gather performance information about VMware Infrastructure ESX servers.

ZenPacks.zenoss.EsxTop-5.0.5_1.1.1-1.lbn19.noarch

The VMWare ESX Server ZenPack for Core allows you to monitor ESX hosts and guests via VMWares EsxTop utility. The ZenPack uses the resxtop command to gather performance information about VMware Infrastructure ESX servers.

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.

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.