The latest packaged version of Zenoss Core Beta for 2.1, Release 2.0.90, is available for download.
More information can be found here http://www.zenoss.com/zenoss-core-2-1-beta/ Zenoss Beta for Core 2.1 is available from: http://www.zenoss.com/download. Zenoss Core 2.1 marks a significant update for many areas of Zenoss Core, including overall look and feel, back-end performance enhancements and added functionality. This is beta release for testing purposes only! DO NOT USE IN PRODUCTION. Please report all issues you find with the release to the zenoss-users forum (http://community.zenoss.com/forums/) or to the mailing list ([email protected]) and please include the word "BETA" in the subject line. The Zenoss 2.1 Beta release 2.0.90 includes several major enhancements as well as many minor fixes detailed below: Network Map * Ever wanted to drag a Flash representation of your network's layer 3 topology around with your mouse? Now you can! From the left navigation menu, select Network Map to see Zenoss make your dreams come true. Google Maps View of Network Health * The new Google maps interface shows you location status and the WAN connections between locations. To access the Google Map of a network Location, navigate to the Location where you want to see the network map, and click the Map tab. Aggregate status of each Location is signified by the color of the node on the map. Additionally, WAN links between devices in different Locations will appear on the map with a color indicating their status. You will need to generate a Google Maps API key per Zenoss instance (not per user). Instructions will prompt you if you do not have one installed. You set the API Key using Settings from the left navigation menu, and then the Settings tab, near the bottom is the place to enter the Google Maps API key. Maps drawn in Zenoss using the Google Maps API will display WAN links between devices in different Locations. As an example, move two devices in the same network to two Location organizers that have the Address attribute set. Bring up the Map tab for the parent of one of those Locations; a green line will appear, linking the two map nodes. Now add an event (Events > Global Menu > Add Event...) on one of the interfaces that makes up the link (e.g., eth0) with a "Critical" severity. Refresh the Map page you were looking at before; notice that the link has become red to indicate that there is a problem with one of its endpoints. Drag 'n' Drop Dashboard * The Zenoss dashboard, once a source of dismay, is now a delightful place to play. You can now configure the dashboard to your satisfaction, choosing from an array of helpful portlets. You can change the arrangement and size of these portlets at will; Zenoss saves the state automatically. You can choose from the following portlets: Google Maps Zenoss Object Watch List Device Issues Heartbeats New Device Icons * Devices and organizers now have icons. You can set Device icons via the zIcon zProperty. These icons are used throughout several of the new features, including the Device status page, the Dashboard, and the Network Map. Device Status Tab Refresh * The Device status tab has been updated to display more information in a more readable way. The most important information about a device is now up at the top. Component issues are shown in a handy table. Graph Improvements * Zenoss 2.1 gives you finer control over performance graph creation and appearance. Graphs are composed of one or more Graph Points, each one of these graph points representing either a DataPoint, a Threshold or a custom RRD graph command. For experienced RRD users, Zenoss 2.1 now provides a graphical interface to creating GraphPoints that contain any of the standard RRD data or graph commands. You can see these improvements wherever graphs are defined in performance templates. Graph Reports * Graph Reports allow you to create a performance report that combines graphs from different devices and components. From the left navigation menu, you choose Reports and then Graph Reports. Add Graph Reports from the table menu and then you can edit and define them from the resulting pages. You choose a device or component and then add one or more of the graphs available for that device/component to the Graph Report. You can repeat this as many times as you want with varying devices/components adding them to the same graph. Multi-Graph Reports * With Multi-Graph reports you can view performance graphs from multiple devices or components on the same report, similar to Graph Reports but with two important advantages. First, the Graphs are defined in the report itself rather than selected from existing graphs defined within Performance Templates. Also, the data from these multiple devices and components can be combined into a single graph. For example, you may want to create a graph that aggregates all the traffic through multiple routers onto a single graph. To create Multi-graph reports, choose Reports from the left navigation menu and then Multi-Graph reports. Then, from the Reports Choose Add New Reports. Here, you can define a graph the same way you would define a graph in any other performance template. JMX Performance Collector * Zenoss Core now includes Java Management Extension (JMX) Performance collection for better monitoring of your Java environments. Any information that an mbean provides can be collected and stored in an RRD file just like other Zenoss collectors. Recurring Sending of Alerts until Event is Acknowledged * When an event is active (not acknowledged) we now allow alerts to be sent repeatedly until the event is acknowledged (if set by the user). Emailing of Zenoss Reports * You can now send URL Pages such as to reports using a new command line tool. When logged into the Zenoss system, you can mail a report using a new command line tool. The syntax to mail a report looks like this: usage: reportmail -u http://xxxx.xxx.xxx/xxx -U userA -P zzzzz The command above will email the report located at "http://xxxx.xxx.xxx/xxx"; to the email address specifed for user "userA" whose password is "zzzzz". Options: -u Specify the URL for the report -U Username to whom you want to mail the report -P Password for that user -a Use before each additional email Send Events From the Command Line to Zenoss * Zenoss 2.1 has a new command-line program for sending events to Zenoss. This script only relies on python, so it can be moved easily to other systems. zensendevent uses the following options: usage: zensendevent [options] summary words Options: -d, --device default: the local fully-qualified domain name -p, --component component from which this event is sent, default: '' -s, --severity default is Warn severity of this event: Critical, Error, Warn, Info, Debug, Clear) -c, --class event class for this event, default: '' --port xmlrpc server port, default: 8081 --server xmlrpc server, default: localhost --auth xmlrpc server auth, default: admin:zenoss Example: zensendevent -c /App/Fail -p sky -s Critical Onos\! the sky is falling\! Device Class Transforms * Users can add transforms to event classes to alter events that do not have an event class key. Zenhub * Zenhub is more resilient in the face of MySQL errors. ZenperfSNMP * Changed zenperfsnmp to load its configuration incrementally to increase responsiveness of zenhub for other services. ZenProcess * Zenprocess now respects the zMaxOids property. ZenDisc * Zendisc now attempts SNMP version 2c and SNMP version 1. Other Fixes * Windows collectors now use IP addresses in addition to their name. * Devices can be found via their management IP address. * Clear events that don't actually clear any events are ignored. Enjoy! --Zenoss Dev Team -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=10837#10837 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
