Modified items

All recently modified items, latest first.

zenoss-protobuf-4.2.5-6.lbn25.noarch: Zenoss ZenEventPer and Impact protocol connectors

zenoss-parent-4.2.5-1.5.lbn25.noarch: Parent POM file for Zenoss Specs.

zenoss-jars-4.2.5-1.13.lbn25.noarch: Maven is a complete crock of shite and we are still figuring out how to build some critical dependency versions that may not be at the same point release as distro mainline. We are simply deploying the expected versions here.

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

ZenPacks.zenoss.Memcached-4.2.5_1.0.0-1.lbn25.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.LDAPMonitor-4.2.5_1.4.1-1.lbn25.noarch: ZenPacks.zenoss.LDAPMonitor monitors the response time of an LDAP server (in milliseconds).

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

ZenPacks.zenoss.JMXNotificationListener-4.2.5_0.9.1-5.lbn25.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.lbn25.noarch

ZenPacks.zenoss.HPMonitor-4.2.5_2.1.0-1.lbn25.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.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.Docker-4.2.5_1.1.0-1.lbn25.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.DigMonitor-4.2.5_1.1.1-1.lbn25.noarch

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

ZenPacks.zenoss.DellMonitor-4.2.5_2.2.0-1.lbn25.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.ApacheMonitor-4.2.5_2.1.4-1.lbn25.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.AWS-4.2.5_2.5.0.dev0-1.lbn25.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.zenoss-4.2.5-1.lbn25.noarch: The ZenPacks.zenoss python module

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

ZenPacks.rhybudd.alerts-4.2.5_1.0.0-2.lbn25.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)

« Previous 20 items Next 20 items » 1 ... 1721 1722 1723 1724 1725 1726 1727 ... 2336


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

Sections

Modified items