OpenNMS 1.2.3 (stable) Released

Gang:

I am happy to announce that the next stable OpenNMS release, 1.2.3 is  
now available.

It contains some new reports and events, some small bug fixes, and a  
new GUI for scheduling outages. It should be an easy upgrade over 1.2.2.

The complete release notes can be found here:

https://sourceforge.net/docman/display_doc.php?docid=27506&group_id=4141

and the files will be here (as usual Debian and OSX builds lag a bit):

https://sourceforge.net/project/showfiles.php?group_id=4141

The time between stable releases will get longer as the code matures,  
and we are taking special care to insure that the stable branch is  
always ready for production.

<shameless plug time>

OpenNMS is supported in a large part by The OpenNMS Group (http:// 
www.opennms.com) which provides support, training, development and  
services around OpenNMS. We currently serve customers in over nine  
countries.

If tasks like merging the XML configuration files cause you to put  
off upgrading, please note that a commercial support contract  
includes this as part of the service. We always welcome people to use  
our products and we don't expect anything in return, but the more  
support we get the faster and better the code will become.

</shameless plug>

We have a lot of wonderful things planned for OpenNMS. Within the  
next month we will be releasing 1.3.0, our new development release.  
It will include:

1) New alarm support. This is a new way of viewing events. For  
important and/or specific events, you can indicate that they are  
"alarms". Alarms are listed one to a line, so instead of a separate  
line for each event, you will have the first time the event occurred,  
the last time, and a total count.

This is useful on our network, where we have a Linksys router that  
sends an SNMP trap for every connection. Over the span of a few days,  
we might have several hundred thousand events that are now shown on  
one line.

In addition, automatic actions can be configured to act on alarms,  
such as increasing the severity of an alarm that has been  
unacknowledged for a certain amount of time, or correlating "up"  
alarms with "down" alarms, etc.

2) SNMP version 3 support. OpenNMS will be fully SNMPv3 compliant for  
data collection and traps.

3) A new JMX collector. Data collection is currently only implemented  
for SNMP. This feature will allow data to be collected via JMX from  
such products as JBoss.

4) Improvements to availability reporting. The currently appearance  
of the availability reports is being greatly improved.

Much of this functionality is in CVS HEAD at the moment, so feel free  
to try it out.

Thanks again to everyone for making this such a great project.

-T


________________________________________________________________________ 
___
Tarus Balog, OpenNMS Maintainer            Main:        +1 919 545 2553
The OpenNMS Group, Inc.                    Fax:         +1 503-961-7746
Email: [email protected]                   URL: http://www.opennms.org
PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://wiki.opennms.org/tiki-index.php?page=MailingListFaq

opennms-announce mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-announce