Modified items

All recently modified items, latest first.

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.

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

ZenPacks.zenoss.EsxTop-4.2.5_1.1.0-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.Docker-4.2.5_1.1.0dev-1.lbn19.noarch: Adds modeler plugin and monitoring datasource to retrieve list of Docker containers and monitor their statuses. Docker Containers modeled in Zenoss device

ZenPacks.zenoss.DnsMonitor-4.2.5_2.1.0-1.lbn19.noarch

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

ZenPacks.zenoss.DeviceSearch-4.2.5_1.2.0-1.lbn19.noarch

ZenPacks.zenoss.DellMonitor-4.2.5_2.2.0-1.lbn19.noarch: DellMonitor provides custom modeling of devices running the Dell OpenManage agents. It also contains hardware identification for Dell 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, voltage) * PCI Card Information (manufacturer, model)

ZenPacks.zenoss.Dashboard-5.0.5_1.0.7dev-4.lbn19.noarch: This ZenPack introduces a new widget framework for creating portlets and sharing dashboards. Users may define any number of portlets and dashboards, which may be shared globally or with specific groups.

ZenPacks.zenoss.DRBDMonitor-4.2.5_1.0.0-1.lbn19.noarch

ZenPacks.zenoss.CloudStack-4.2.5_1.0.9-1.lbn19.noarch: The easiest way to start monitoring CloudStack is to navigate to the Infrastructure page, click the *+* menu to add a device and choose Add CloudStack. Fill out the URL, API Key, and Secret Key fields then click OK. The URL should only include the protocol, host and port (i.e. http://cloudstack.example.com/). You can find or create the keys by logging into the CloudStack web interface and navigate to Accounts and users. Zenoss will then add the CloudStack device to the system along with all of its associated zones, pods, clusters, system VMs and VMs. Monitoring will also start after the discovery is complete. Metrics Once you've successfully added a CloudStack cloud to Zenoss you will begin to see the following metrics available for the entire cloud. These numbers are aggregated from all zones, pods, clusters and hosts. Public IPs: Total and Used Private IPs: Total and Used Memory: Total (with and without over-provisioning), Allocated and Used CPU: Total (with and without over-provisioning), Allocated and Used Primary Storage: Total (with and without over-provisioning), Allocated and Used Secondary Storage: Total and Used Network: Read and Write The same list of metrics are available for each zone. The same metrics with the exception of public IPs and secondary storage are also available for each pod. The following metrics are available aggregated to each cluster, and for each host. Memory: Total and Used CPU: Total (with and without over-provisioning), Allocated, Used and Cores Network: Read and Write Events CloudStack has both alerts and events. Once you've successfully added a CloudStack cloud to Zenoss you will automatically receive all CloudStack alerts as events in Zenoss. You will also automatically receive all CloudStack events. However, the events will go straight into your event history by default. To avoid overloading CloudStack and Zenoss, only the last two (2) days of events will be checked. This allows for timezone discrepency between the Zenoss and CloudStack servers as well as some downtime without missing events. There is no real-time event collection mechanism with the CloudStack API, so alerts and events will only be polled once per minute. Installed Items Installing the ZenPack will add the following items to your Zenoss system. Device Classes /CloudStack Configuration Properties zCloudStackURL zCloudStackAPIKey zCloudStackSecretKey Modeler Plugins zenoss.CloudStack Monitoring Templates Cloud Zone Pod Cluster Host Event Classes /Status/CloudStack /Perf/CloudStack /App/CloudStack

ZenPacks.zenoss.CloudFoundry-4.2.5_1.0.4-1.lbn19.noarch: This ZenPack makes it possible to monitor the capacity and performance of applications running on a Cloud Foundry platform. This works for applications hosted in a local micro-cloud or a hosted environment such as the one offered by VMware at cloudfoundry.com. Cloud Foundry is an open PAAS (Platform as a Service) project initiated by VMware. Usage Once the CloudFoundry ZenPack is installed you can add endpoints by going to the infrastructure screen and clicking the normal button for adding devices. You will find a new option labeled, "Add CloudFoundry Endpoint." Choose that option and you'll be presented with a dialog asking for the following inputs. Target - An example would be api.cloudfoundry.com or api.vcap.me. Email - The email address you used to register. Password Once you click Add Zenoss will contact the target and get all of the operationally interesting information that exists. Once it is complete you'll find a new device in the /CloudFoundy device class with the same name as the target you entered into the dialog. Click into this new device to see everything that was discovered. The following elements are discovered: Frameworks Runtimes App Servers System Services Provisioned Services Apps App Instances The following performance metrics are collected: Per-Endpoint (target) Limits App URIs Apps Memory Services Usage App URIs Apps App Instances Running App Instances Memory Services Utilization App URIs Apps Memory Services Per-App Resources Memory Disk Usage CPU (average across instances) Memory Disk Utilization Memory Disk Instances Total Running Services URIs Per-App Instance Quota Memory Disk Usage CPU Memory Disk Utilization Memory Disk The following default thresholds are configured: Over 99% utilization of.. Endpoint App URIs Endpoint Apps Endpoint Memory Endpoint Services App CPU (average across instances) App Memory App Disk App Instance CPU App Instance Memory App Instance Disk Less than 1 running instance per App

ZenPacks.zenoss.CalculatedPerformance-5.0.5_2.1.0dev-4.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.ApacheMonitor-4.2.5_2.1.4-1.lbn19.noarch: ApacheMonitor ------------- ApacheMonitor provides a method for pulling performance metrics from the Apache HTTP Server (http://httpd.apache.org/) directly into Zenoss without requiring the use of an agent. This is accomplished by utilizing the standard mod_status module that comes with version 1 and 2 of the HTTP server. The following metrics will be collected and graphed for the Apache HTTP Server. * Requests per Second * Throughput (Bytes/sec & Bytes/request) * CPU Utilization of the HTTP server and all worker processes/threads * Slot Usage (Open, Waiting, Reading Request, Sending Reply, Keep-Alive, DNS Lookup and Logging) Follow these steps to setup your HTTP server so that it will allow Zenoss to access the server status. 1. On the Apache server, find your httpd.conf file. This is normally located in /etc/httpd/httpd.conf or /etc/httpd/conf/httpd.conf. Other locations are possible depending on your operating system and setup. 2. Turn the ExtendedStatus option on in the httpd.conf file. This option will typically be commented out. You can enable it by uncommenting it. ... becomes ... ExtendedStatus on 3. Enable the /server-status location in the httpd.conf file. This is another option that typically already exists but is commented out. ... becomes ... <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from zenoss.yourdomain.com </Location> 4. Save the httpd.conf file with these changes then restart httpd. This can normally be accomplished with following command. apachectl restart Once your Apache HTTP Server is configured to allow Zenoss to access the extended status, you can add Apache monitoring to the device within Zenoss by simply binding the Apache 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 Apache template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Apache HTTP Server metrics from this device.

ZenPacks.zenoss.ActiveDirectory-4.2.5_2.1.0-1.lbn19.noarch: This Zenpack: - Creates a device class for Microsoft Active Directory with appropriate priorities. - Creates Windows Service and IP Service classes for Active Directory-related services with monitoring enabled. - Monitors the following metrics: DS Client Binds/Sec DS Directory Reads/Sec DS Directory Searches/Sec DS Directory Writes/Sec DS Monitor List Size DS Name Cache Hit Rate DS Notify Queue Size DS Search Sub-operations/Sec DS Server Binds/Sec DS Server Name Translations/Sec DS Threads In Use KDC AS Requests KDC TGS Requests Kerberos Authentications LDAP Active Threads LDAP Bind Time LDAP Client Sessions LDAP Closed Connections/Sec LDAP New Connections/Sec LDAP New SSL Connections/Sec LDAP Searches/Sec LDAP Successful Binds LDAP UDP Operations/Sec LDAP Writes/Sec NTLM Authentications

ZenPacks.zenoss.AWS-4.2.5_2.2.2dev-1.lbn19.noarch: This ZenPack provides support for monitoring Amazon Web Services (AWS). Monitoring for the following EC2 entities is provided through a combination of the AWS EC2 and CloudWatch APIs. Features The features added by this ZenPack can be summarized as follows. They are each detailed further below. Discovery of EC2 entities. Monitoring of CloudWatch metrics. Optional auto-discovery and monitoring of instance guest operating systems. Optional service impact with addition of Zenoss Service Dynamic product. Discovery The following entities will be automatically discovered through an account name, access key and secret key you provide. The attributes, tags and collections will be updated on Zenoss' normal remodeling interval which defaults to every 12 hours. Regions Attributes: ID Collections: VPCs, Subnets, Zones, Instances, Volumes Zones Attributes: ID, Region, State Collections: Instances, Volumes, Subnets VPCs Attributes: ID, Region, CIDR Block Tags: Name, Collector Collections: Subnets, Instances Subnets Attributes: ID, Region, VPC, Zone, State, CIDR Block, Available IP Address Count, Zone Default, Auto-Public IP Tags: Name Collections: Instances Instances Attributes: ID, Region, VPC, Zone, Subnet, State, Instance Type, Image ID, Platform, Public DNS Name, Private IP Address, Launch Time, Guest Device Tags: Name Collections: Volumes Other: Guest Device (if monitored by Zenoss) Volumes Attributes: ID, Region, Zone, Instance, Type Created Time, Size, IOPS, Status, Attach Data Status, Attach Data Device Tags: Name Monitoring The following metrics will be collected every 5 minutes by default. Any other CloudWatch metrics can also be collected by adding them to the appropriate monitoring template. The Average statistic is collected, and the graphed value is per second for anything that resembles a rate. Regions Metrics: CPUUtilization, DiskReadOps, DiskWriteOps, DiskReadBytes, DiskWriteBytes, NetworkIn, NetworkOut Instances Metrics: CPUUtilization, DiskReadOps, DiskWriteOps, DiskReadBytes, DiskWriteBytes, NetworkIn, NetworkOut, StatusCheckFailed_Instance, StatusCheckFailed_System Volumes Metrics: VolumeReadBytes, VolumeWriteBytes, VolumeReadOps, VolumeWriteOps, VolumeTotalReadTime, VolumeTotalWriteTime, VolumeIdleTime, VolumeQueueLength Provisioned IOPS Metrics: VolumeThroughputPercentage, VolumeReadWriteOps The Amazon CloudWatch datasource type also allows for the collection of any other CloudWatch metric. Guest Device Discovery You can optionally configure each monitored AWS account to attempt to discover and monitor the guest Linux or Windows operating systems running within each EC2 instance. This requires that your Zenoss system has the network and server access it needs to monitor the guest operating system. VPC and non-VPC modes are supported. The guest operating system devices' life-cycle are managed along with the instance. For example, the guest operating system device is set to a decommissioned production state when the EC2 instance is stopped, and the guest operating system device is deleted when the EC2 instance is destroyed. Service Impact When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for services running on AWS. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities. Service Impact Relationships Account access failure impacts all regions. Region failure affects all VPCs and zones in affected region. VPC failure affects all related subnets. Zone failure affects all related subnets, instances and volumes. Subnet failure affects all instances on affected subnet. Volume failure affects any attached instance. Instance failure affects the guest operating system device. Usage Adding AWS Accounts Use the following steps to start monitoring EC2 using the Zenoss web interface. Navigate to the Infrastructure page. Choose Add EC2 Account from the add device button. Enter your AWS account name, access key and secret key. Optionally choose a collector other than the default localhost. Click Add. Alternatively you can use zenbatchload to add accounts from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple accounts can be added under the same /Device/AWS/EC2 section. /Devices/AWS/EC2 loader='ec2account', loader_arg_keys=['accountname', 'accesskey', 'secretkey', 'collector'] <accountname> accountname='<accountname>', accesskey='<accesskey>', secretkey='<secretkey>', collector='<collector>' You can then load the account(s) with the following command. $ zenbatchload <filename> Configuring Guest Device Discovery Use the following steps to configure instance guest device discovery. Guest device discovery must be configured individually for each EC2 account. Navigate to one of the EC2 accounts. Click the edit link beside Device Class for Discovered Linux Instances Choose the device class for Linux and/or Windows instances. Verify that appropriate SSH, SNMP or Windows credentials are configured for the chosen device class(es). Remodel the EC2 account by choosing Model Device from its menu. If your instances are VPC instances, and are in a different VPC than the Zenoss server that's monitoring the EC2 account, you must add a Collector tag to containing VPC with the value set to the name of the Zenoss collector to which discovered guest devices should be assigned. Installed Items Installing this ZenPack will add the following items to your Zenoss system. Device Classes /AWS /AWS/EC2 Modeler Plugins aws.EC2 Datasource Types Amazon CloudWatch Monitoring Templates EC2Region (in /AWS/EC2) EC2Instance (in /AWS/EC2) EC2Instance-Detailed (in /AWS/EC2) EC2Volume (in /AWS/EC2) EC2Volume-IOPS (in /AWS/EC2) Device Types EC2Account (in /AWS/EC2) Component Types EC2Region (on EC2Account) EC2VPC (on EC2Region) EC2VPCSubnet (on EC2Region) EC2Zone (on EC2Region) EC2Instance (on EC2Region) EC2Volume (on EC2Region)

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

« Previous 20 items Next 20 items » 1 ... 1934 1935 1936 1937 1938 1939 1940 ... 2449


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

Sections

Modified items