This Week in OpenNMS, Friday February 13th

Welcome to This Week in OpenNMS for Friday the 13th. It’s yet again time to take a look at what’s been going on in the world of OpenNMS development.

Project Updates

  • Stable: Current Release is 1.6.2

    1.6.2 is still the current release, and while there are a few fixes pending since it’s release, there are no immediate plans for a 1.6.3 yet.

  • Unstable: Current Release is 1.7.0

    Trunk has been moving fast still, and I hope we’ll get a 1.7.1 release out soon-ish, but we’re still trying to get provisiond up to a demoable state first. In the meantime, feel free to try the nightly snapshots (if it’s not on a production system, of course).

  • Trunk: Javamail Updates

    Dave’s been working on refactoring our javamail support into it’s own module, to make it easier to reuse in different portions of OpenNMS.

  • Trunk: RANCID Integration

    Guglielmo continued work on the RANCID integration; the API has stopped changing much and most of the work has been going on in the UI at this point.

  • Trunk: Provisiond

    Matt has most of the provisiond code working, some simple scanning is possible now, there are just a few loose ends to tie up before there’s a working prototype.

  • Trunk: Node Page Updates

    Donald’s spiffy new ajaxy node page is active, and lets you page through data related to the node directly in the node page.

  • 1.6 Testing: Minor Updates

    Jeff, Bill, and a few others have done some minor updates to 1.6-testing (which of course are forward-ported to trunk as well) including IE rendering issues, additional MIBs, read-only KSC report support, and more.

  • Trunk: Map Updates

    Antonio has continued work on the new trunk map code, which includes support for all modern SVG browsers (Safari, Firefox, and IE with the Adobe SVG plugin).

  • Trunk: RESTful Support for Map Data

    Matt Raykowski submitted RESTful API support for map and related data (map elements, linkd data, etc.) which will be useful for future map work.

  • Trunk: XMP/Cartographer Support

    Jeff merged Bobby Krupczak’s Cartographer agent support for OpenNMS to trunk.

    Cartographer “implements a novel approach to managing distributed systems by automatically discovering and tracking the relationships between its component systems and applications. Cartographer does so via specially designed agents — residing on clients, servers and (potentially) network devices — that detect, identify, and track the inter and intra-system dependencies or relationships. Dependencies include network level services like DNS, DHCP, and SMTP as well as higher-level application abstractions like filesystems, databases, directory services, telephony, and middleware.”

Upcoming Events

If you have anything to add to the events list, or you wish to be a Dev-Jam sponsor, please let me know.

If You Can’t Love the Source You’ve Opened, Open the Source You Love

That’s all for this week. I hope you all have a wonderful valentine’s day if you’re into that kind of thing. As always, feel free to drop me a line if you have any questions, comments, or if you wish to know my address so you can send me some mysterious white powder through postal mail.

Share on Facebook

This Week in OpenNMS, Friday January 30th

It’s time for another This Week in OpenNMS. I will be skipping next week’s, as I’ll be too busy sunning myself in the caribbean and hanging out with a bunch of rockin’ bands on Ships and Dip V. Ahhhhh….

Project Updates

  • Stable: Current Release is 1.6.2

    1.6.2 seems to be holding up nicely, although there have been some reports of issues with JMX thresholding that need to be investigated more deeply still. If you’re having issues and can add some details to the bug on the subject, it would be appreciated.

  • Unstable: Current Release is 1.7.0

    Trunk is still moving crazy fast, so hopefully we’ll be getting another 1.7 release out there soon when a few things settle down, so people can help test. In the meantime, feel free to try the nightly snapshots (if it’s not on a production system, of course).

  • Trunk: Acknowledgement Daemon

    Dave continues to make progress on Ackd in between crazy days at the TeleManagement Forum’s Team Action Week (more on that later). Hopefully it will be ready for folks to test it out in the next few weeks.

  • Trunk: Inventory Daemon

    Fresh off the heady high of getting WMI support in trunk, Matt Raykowski has started work on on inventory daemon, which intends to provide a more flexible interface to systems asset and inventory information than our current (anemic) asset system.

  • Trunk: Provisiond

    Provisiond continues to progress towards something usable. Matt’s been working on finishing the scanning code, and Matt and I both have spent some time this week making an optimized SNMP table tracker which will let us perform operations on collected SNMP data as it comes in, so scans of nodes with large numbers of interfaces will happen in a more timely manner.

    I also finished up this week a RESTful API to the Provisiond importer, which will let you edit and create model-import and foreign sources. The web UI is next, and will use this API for creating provisiond’s configuration.

  • Trunk: RANCID Support

    Guglielmo continues to flesh out the RANCID API. Work has begun on the OpenNMS web UI side of the implementation, and small changes are still being made to the RANCID java bindings.

  • Trunk: Node Page Updates

    Donald continued his work on making the node page more dynamic.

TeleManagement Forum’s Team Action Week

OpenNMS, represented by OGP members Craig Gallen and David Hustace, is participating this week at the TeleManagment Forum‘s (TMF) Team Action Week (TAW) in Lisbon.

Craig is leading the TMF Interface Program (TIP) Reference Implementation (RI) team and we will be creating open source implementations of TIP interfaces starting with Service Problem Management (SPM).

The artifacts created by the reference implementation team will be libraries that can be used to develop NGOSS-compliant components in service provider applications. OpenNMS has committed to working on the Service Problem Management (SPM) interface (Alarms), Inventory, Performance Management, and Trouble Ticket implementations. For more information see the interface program page on TMF’s web site.

Upcoming Events

If you have anything to add to the events list, or you wish to be a Dev-Jam sponsor, please let me know.

Cruisin’

That’s it for now. We’ll see you again, in a couple of weeks! As always, if you have questions, comments, or angry hate-filled missives to send, let me know.

Share on Facebook

This Week in OpenNMS, Friday January 23rd

Sorry I missed last week, I ended up having so much come up I didn’t have time to put it together, so this issue is an action-packed 2-week OpenNMS extravaganza!

Project Updates

  • Stable: Current Release is 1.6.2

    On January 15th, we saw the release of OpenNMS 1.6.2 which included a number of small bugfixes and feature additions.

    For the full list of what was changed, see the 1.6.2 bug milestone.

  • Unstable: Current Release is 1.7.0

    The 15th also saw the first unstable release since 1.6 went stable. It is a work-in-progress release from trunk which gives a preview of the features to come in the 1.8 series. As 1.7.x releases come out, the release notes in the New and Noteworthy section of the web page will be updated with an overview of the new features which will be in 1.8.0.

  • Trunk: Provisioning

    Provisiond is moving along, with lots more commits. Matt has been working on the scheduler and other infrastructure, and I’ve been working on the data model for the requisition (what nodes/etc. to import) and foreign source (what to do with the information imported). Things are moving along, and hopefully we will be doing actual scanning of node data soon.

  • Trunk: RANCID Integration

    Guglielmo has been working more on the integration with RANCID for Cisco router management.

  • Trunk: Acknowledgement Daemon

    Dave is continuing his work on the acknowledgement daemon. It’s approaching finished, and will hopefully be in a usable state in the nightly snapshots soon.

  • Trunk: WMI Updates

    More work has been done on the WMI feature since 1.7.0 came out, including some architectural tweaking, and lots of new data collections.

  • Trunk: Map Work

    More work has been going on in the OpenLaszlo map branch. From what I’ve been told, it’s approaching a usable/demoable state. Look for updates on this soon!

    Also, Antonio did some bugfixes and updates to the Firefox/Safari SVG maps, as well.

  • Trunk: Node Page Enhancements

    Donald has been working on some new spiffy dynamic node pages which will allow you to browse node data, do simple queries, and other neat stuff, using Ext JS.

  • Trunk: Asterisk Notification Support

    Jeff added support for notifications through Asterisk.

Upcoming Events

If you have anything to add to the events list, or you wish to be a Dev-Jam sponsor, please let me know.

Adieu

That’s it for this week. As always, questions, comments, constructive and/or destructive criticism are always welcome. =)

Share on Facebook

This Week in OpenNMS, Friday January 9th

The holidays are over, the hangovers have been recovered from, and in the meantime, a flurry of activity has been happening in the OpenNMS world. It’s time for another This Week in OpenNMS!

Project Updates

  • Stable: 1.6.2 Coming

    The goal is to release version 1.6.2 next week. There have been a number of bugs fixed (and a few small features added) since 1.6.2.

  • Trunk: Provisioning

    Work continues on the new provisioning code at a frantic pace. We’re not yet at a milestone where people can use it, but lots of pieces are coming together.

  • Trunk: Acknowledgement Daemon

    Dave has begun work on Ackd, the OpenNMS acknowledgement daemon. This will allow API and user-interactive access to acknowledging alarms. The goal is to be able to acknowledge alarms through jabber, email, etc. upon receiving a notification of an issue.

  • Trunk: Alarm Daemon

    Dave also worked on Alarmd, a daemon for managing persistence of alarms to improve event persistence performance and reduce delay in forwarding events
    to listeners.

    This immediately began discussions with a large Telco in Europe about their contributing a 3GPP compliant alarm strategy. Cool.

  • Trunk: IRC Notification Strategy

    DJ committed a notification strategy that can notify you of events and outages through IRC chat.

  • Trunk: Event Code Updates

    Antonio committed some updates to the event code allowing expanding varbinds in an event log message, as well as some changes to the event proxy.

  • Trunk: Cross-Browser Map Support

    Antonio also committed a first-blush update of the OpenNMS map support that works with Safari and Firefox. It still needs some work, but is in a usable state now.

  • Trunk: WMI Has Landed

    WMI support has landed in trunk! Thanks to Matt Raykowski for the hard work in implementing this much-requested feature!

    It supports polling and datacollection, and through the magic of j-Interop, it is completely platform-independent. You do not need to be running OpenNMS on Windows or have any kind of special proxy to collect WMI information from remote hosts, it’s a pure-java client implementation using native DCOM to Windows hosts.

  • Trunk: 1.7.0 Coming

    Alongside 1.6.2, we’re looking forward to putting out our first unstable release in the 1.7 series. Considering all of the great work that has happened since 1.6 was branched, it was deemed time to make a release and get it out there for people to test. Look for it soon!

Order of the Green Polo Nomination: Matt Raykowski

In honor of his awesome WMI contribution, Matt Raykowski has now been added to the ranks of the Order of the Green Polo. The OGP is an organization of folks who have made a significant contribution to OpenNMS.

Welcome, Matt, and thank you!

Upcoming Events

There has also been discussion of a user conference during the February training dates in Italy, but it’s not yet been finalized. Stay tuned to the opennms-announce list for details when we have them.

If you have anything to add to the events list, please let me know.

Whew

That’s it for this week. Tune in next week for another exciting installment.

Will we get 1.6.2 and 1.7.0 out on time? Will we create a provisioning system that can take down the Internet? Will we find out how Jeff was able to grown an extra set of hands to answer support tickets on two computers at once? Find out next Friday on This Week in OpenNMS!

Share on Facebook

This Week in OpenNMS, Friday December 19th

It’s been a pretty busy week here in OpenNMS land.

Project Updates

  • Stable: RT Ticketing Plugin

    Jonathan got his RT ticketing updates finished, along with some OTRS cleanup. These have been merged back into trunk and the 1.6-testing branch, so should be ready pending a review, for the 1.6.2 release.

  • Stable: More Vendor Traps

    Jeff spent some time adding more SNMP collection, graphs, and trap events for a number of agents, including SNMP Informant and AIX.

  • Trunk: IfIndex Persistence

    Antonio committed a small change to the event and alarm persistence code to allow Trapd to extract IfIndex from varbinds if it is available.

  • Trunk: Provisioning

    We continued to focus on the new provisioning daemon and API, with a lot of design work and pair programming going on, especially on Matt’s part. We all spent time this week breaking the work up into smaller chunks so we can get a better idea of what our progress is.

    Donald continued to work on the detector code, adding more detectors, tests, and cleanups to the existing code.

    I’ve been working on creating the model for the configuration that will drive provisioning, including changing the default plugin behavior, defining custom behaviors for determining which IP and SNMP interfaces will be managed (as well as what categories the nodes will be put into). I’ve been learning much about JAXB along the way, which gives us an alternative to all of the intermediate wrapper code we tend to have to put around our existing Castor model objects.

    David’s been working on mocking up some code that will allow the provisioning system to automatically update a dynamic DNS server with information discovered during provisioning.

  • Trunk: WMI Support

    Matt Raykowski continued to work on putting some finishing touches on the WMI support. There’s some more to do, but he’s hoping to get a first drop of it released into trunk any day now.

  • Trunk: RANCID Integration

    Guglielmo committed the starts of what will become an implementation with RANCID, a tool for doing change management and configuration on Cisco devices.

    The first part wraps the existing (Tcl-based) RANCID tools with a web-services API. Next, we will be writing a plugin for the new provisioning API that can be called when managed node information changes.

  • Other: Laszlo Maps

    Matt Raykowski also spent some time in a branch he and Joed have been working on to create network topology maps using OpenLaszlo. It’s not yet ready for integration into trunk, but a lot of good low-level work has been going on in that branch alongside the maps work.

  • Other: Web UI Work

    Rob Moore committed some updates to Matt’s sandbox “expenses” application (a codebase to test out new technologies) which include a data grid and a sample query interface using JOSQL. We saw a preview of this at Dev-Jam this year, and it looks pretty sweet. Hopefully we can get it integrated into the OpenNMS web UI in the future.

Upcoming Events

Note: The OpenNMS Group is running a special until the end of the year. Sign up for basic support and get one basic training voucher, sign up for enterprise support (including upgrading from basic) and get a combined basic/advanced training voucher. See Tarus’s “Forget TARP, Take COVER” post for details.

If you have anything to add to the events list, please let me know.

‘Zat You, Santa Claus?

That’s it for this week.

The OpenNMS Group is off from Christmas to the new year, so things will probably be quiet next week. I want to wish you all a happy non-denominational, non-specific, non-offensive, winter solstice time celebration day!

As always, feel free to drop a comment my way if you have any suggestions, love- or hate-mail, or anything at all.

Share on Facebook

This Week in OpenNMS, Friday December 12th

So far the response has been positive to TWiO, so it’s time again for another chapter.

Project Updates

  • Stable: Ticketing Updates

    Jonathan Sartin worked more on the OpenNMS trouble-ticketing API, finishing up a change to allow ticketer plugins to be able to raise exceptions when errors occur. In addition, he resurrected work on an RT (Request Tracker) ticketer plugin. Both will be merged to the 1.6 branch when they’re ready.

  • Stable: Bug Fixes

    I spent a little time this week cleaning up some bugs, mostly exceptions, simple bugfixes, and other minor changes.

  • Stable: Windows Updates

    Bobby Krupczak was kind enough to lend a Win64 machine with Visual Studio so I could get 64-bit binaries built. They are available now on SourceForge. (Copy the jicmp and msvcr90 DLLs to your system directory, don’t forget to rename them to remove the -win64 bit.)

    In the process of working on that, a reasonably serious bug was found in the JICMP libraries on Windows. Windows passes around HANDLEs instead of file descriptors for the purposes of file I/O (and socket I/O). We were treating them as if they were normal file handles (ie, integers), which just happened to work on Win32, not because it was correct, but because we didn’t try to access the filehandle from Java directly. :) The code has now been cleaned up to treat socket operations on HANDLEs (well, SOCKETs) properly on Windows, and the new DLLs in the JICMP 1.0.9 binary release contain these changes (win32 and amd64).

    Additionally, it was determined that Windows XP, at least, is pickier about reading from raw sockets than other platforms, and requires that at least one packet is sent out the socket before reading any in (even though we’re just listening for any ICMP packets on the raw socket, so it shouldn’t really matter). This is fixed in the jicmp.jar in the 1.0.9 distribution; until 1.6.2 comes out, it is recommended you copy this jar over the one included in $OPENNMS_HOME/lib if you are running on Windows.

  • Trunk: More Work on the New Provisioner

    Donald continued implementing “detectors”, the equivalent of Capsd’s protocol plugins, including a new asynchronous API which will allow us to interact with services at a much more granular level.

    Matt has proposed we use more agile development practices, and towards that goal, he started working on a document describing the current desired featureset of the provisioner. We’ve broken it up into chunks which will then be used to do code sprints so we can do a better job of divvying up the work. We’re working on going through and cleaning up the documentation and hopefully we’ll get it into the wiki soon.

  • Trunk: Refactoring Maven (Services)

    Right now, one of the biggest chunks of code in our source tree is “opennms-services“. It’s kind of a dumping-ground of all of the high-level code that isn’t webapp code, and it’s a bit unweildy. I’ve started a branch to attempt to refactor at least some of it into smaller chunks (splitting out capsd, collectd, config, eventd, mock, notifd, poller, threshd, trapd, xmlrpcd, and so on). Work will be ongoing, but hopefully eventually we’ll have things a bit more manageable.

  • (Almost) Trunk: WMI Support

    Matt Raykowski has been finishing up work on his WMI (Windows Management Instrumentation) monitor and collector and we hope to be merging it into trunk in the near future. There are just a few more finishing touches to put on it, and then it will be ready for inclusion in the future 1.8 release.

Upcoming Events

(Or, as Tarus calls it, Git Yer Learnin’ On.)

If you have anything to add to the events list, please let me know.

Development: A Brief Interlude

It’s time for a little aside on some of the tools we use for development.

Maven is an awesome tool, but with a large project like OpenNMS, checking repositories and other things are actually a significant drag on the build process. To help alleviate this (and to speed up building and sharing artifacts on our Bamboo continuous-integration server) we set up a Nexus proxy at the office. It worked so well, I set one up at home too. =)

If you’d like to set up your own, I’ve documented what we did on the OpenNMS wiki. Feel free to update it (and/or ask questions) if you run into any issues.

And on the subject of Bamboo, I realized I haven’t yet publicly thanked Atlassian for their generosity. They’ve generally been very generous to open-source projects, offering free licenses for their tools (continuous integration, bug tracking, etc.) OpenNMS has a very large build, and it can take a long time to work it’s way through the continuous-integration process even with a fast machine. They were kind enough to extend our open-source license to allow for more than the usual number of agents, and we’re now burning rubber with our entire set of classroom machines acting as build agents. No longer do we have huge queues of waiting builds, we get very timely Jabber notices when we break the build. Hm… maybe that’s not such a good thing after all. ;)

Anyways, thanks again to Atlassian for the license upgrade, it’s working great!

That’s It for This Week

That’s it for now. I hope you’re enjoying these updates. If you have any questions or comments, or if you’ve done something cool with OpenNMS that you’d like included, please let me know.

Share on Facebook

This Week in OpenNMS, Friday December 5th

I was recently remembering fondly the oldskool “OpenNMS Updates” that Shane O’Donnell used to do, and I thought I’d take a crack at reviving the tradition. So, without further ado…

Project Updates

  • Stable: Current Release: 1.6.1

    OpenNMS 1.6.1 seems to be holding up without any huge bugs reported. There are no immediate plans for a 1.6.2 release but I would expect we’ll look into doing one in a month or so just to roll up any bugfixes that have happened, if nothing else.

  • Stable: Configuration Tweaks

    David did some configuration changes that will be in a future 1.6 release which automatically roll up SNMP LinkUp and LinkDown traps into an alarm. Also, Jeff added a bunch of IETF and vendor MIB data collection and graphs to the 1.6 branch.

  • Trunk: Provisiond

    Development is still churning along in trunk, with the focus on the Capsd rewrite. Since this is the first (of hopefully many) TWiO, I will go into a bit more depth.

    OpenNMS has always been written with scalability in the forefront of our minds, but JVM technology and development methodologies have moved a lot since we first started the project 9 years ago. Since the OpenNMS 1.2 series, and even a bit before, many of the subsystems of OpenNMS have been tweaked, cleaned up, and even rewritten for performance and other reasons. One of the things that’s needed attention for quite some time is Capsd, the part of OpenNMS that figures out what devices are on your network, and what those devices’ capabilities are (hence, Capsd).

    Matt Brozowski has been working on a complete replacement, called Provisiond. One of the benefits of the OpenNMS architecture is that it’s event-driven structure with distinct daemons for different subsystems makes it easy to make new implementations without breaking existing things. Thus, Provisiond will be installed (disabled, by default) alongside Capsd in 1.8, and in 1.10 (or 2.0), it will become the default capabilities scanner, with Capsd deprecated but not yet removed.

    The Provisiond architecture is such that a very robust threading model has been introduced to allow scanning huge numbers of resources in a very efficient manner, and the API has been written to make it very simple to implement new “detectors” which detect services and resources.

    Eventually this new architecture can (and should) be extended to polling/monitoring and data collection, but… one thing at a time. ;)

    Anyways, Matt has been rockin’ the Java working on Provisiond, and I’ve been pairing with him off and on. I really like the way this code is shaping up. Donald in the meantime has been making tons of detectors so we can cover the large range of services we already detect with Capsd.

  • Trunk: Mobile UI

    Alexander Finger started work on a simple mobile UI that gives you the outages summary on a single page (at least on my iPhone <g>).

    OpenNMS Mobile UI

Upcoming Events

If you have anything to add to the events list, please let me know.

From the Discussion Lists – Cartographer

[original thread]

Bobby Krupczak has created a tool called Cartographer which “implements a novel approach to managing distributed systems by automatically discovering and tracking the relationships between its component systems and applications.” In addition to the Cartographer protocol (XMP), software, and agent, he has written a collector plugin for OpenNMS which allows the collection and graphing of Cartographer XMP data. Very cool!

Hopefully soon we will get the collector integrated into OpenNMS proper and a future release (1.6 if it’s not too invasive, or at the latest, 1.8).

That’s It!

So that’s it for this week. Let me know if you think this is a useful thing for me to do, if there’s anything you’d like me to talk about that’s missing, or, well, if you have any comments at all. Until next week…

Share on Facebook

PostgreSQL ‘IPLIKE’ Plugin Available for Windows

Since we (regrettably <g>) support a couple of customers running OpenNMS on Windows, I spent some time yesterday getting IPLIKE built on it, finally. You no longer have to rely on the slow PL/PGSQL version of it, and can instead use the nice speedy native C version instead.

For details, see the wiki page for IPLIKE.

As far as I’m aware, there is not a win64 version of PostgreSQL, so I’ve punted investigating what it would take to get stuff built on it, but I would like to get a 64-bit JICMP built at least. Does anyone have a win64 development environment that could get it building for us? I have no Win64 licenses, much less development environment. A little investigating dug up a MinGW64 preview, but I have no idea if it would actually work or not. =)

If you run into any problems with it, let me know!

Share on Facebook

OpenNMS 1.6.0 Is Out

…and it features a ton of changes since the last stable release. Here’s what I put in the release notes as an introduction to the 1.6.0 release:

Release 1.6.0 is the first stable release in the OpenNMS 1.6 series.

It’s been 3 and a half years since the last OpenNMS stable version, 1.2, was branched and released as production-ready. In that time, OpenNMS as a project has changed tremendously, the community has grown exponentially, and massive numbers of new features have been incorporated into the “unstable” 1.3.x series.

In that time, the unstable codebase solidified to the point that The OpenNMS Group supported it as if it were stable; it was at least as stable as 1.2.x was, but many users held off on upgrading because of the unstable moniker.

After a lot of work, and a renewed focus on getting the next stable release out the door, we are now prepared to declare OpenNMS 1.6 release-candidate-ready.

Why 1.6 instead of 1.4? 3 years is a lot of time, and a lot has happened in that time. We’re not ready to call it 2.0, we want to redo the web UI first, but 1.4 didn’t really do the massive changes since 1.2 justice. So: 1.6 it is.

Since it is a lot easier to do a release than it was in the 1.2 series (now that the native code is moved out into separate packages, and OpenNMS itself is distributed as pure-java sources), the goal is to continue to be on a much faster 6-month or year cycle for new releases.

Please, let us know if you have any problems at all in our Bugzilla bug tracker.

To give an idea of what’s changed, I put together a list of major changes since 1.2 with a couple of the other OGP folks.

Architecture and New Subsystems

  • Alarms: The largest architectural change from a user point of view is the addition of the concept of Alarms. Events mean so many different things in OpenNMS, it made sense to have a higher-level “event” which represents significant happenings in the system. Alarms fill that role, and as we move towards 2.0, events will be de-emphasized in favor of alarms for reacting to significant events. The new alarms system will allow important events to be “reduced” into alarms. If an event comes in with the same “reduction key” as a previous event, the alarm will increment the “count” of events, yet it will still only take up a single line in the alarm browser. Clicking on the count will bring up the event browser with just the events that have been reduced.
  • Automations: It is now possible to do a variety of automated actions through “automations”. For example, say you have an alarm with the severity of Minor that has not been acknowledged in the last 20 minutes you might want to escalate the severity. Vacuumd has been enhanced with a configuration that now allows configuration of processes we’re calling Automations that are defined by Triggers and Actions.
  • Windows: OpenNMS now runs on Windows.
  • PostgreSQL: OpenNMS supports running on top of PostgreSQL 7.4 through 8.3.
  • Syslog Improvements: The syslog daemon included with OpenNMS has been significantly enhanced, including regular-expression matching and back-reference support.
  • Model Importer: OpenNMS can now import node, interface, and service information from an external provisioning source. This facility can augment or replace the discovery functionality provided by Capsd.
  • Categories: Nodes can be assigned to one or more categories (eg Production/Test, Datacenter A, Datacenter B); these categories can be used in filter rules. This permits to selectively forward Alarms into certain destination paths based on the node category: “Send Alarms for Production in Datacenter A to Team A, Send Alarms for Test Systems in all Datacenters into the Maintenance Queue”.

Polling and Data Collection

  • Generic-indexed data collection modeling makes it easy to collect, graph, and threshold on multi-instanced performance data, such as values residing in SNMP MIB tables.
  • SNMP4J: In addition to the existing SNMPv1 and SNMPv2 support provided by our in-house JoeSNMP Java library, OpenNMS now supports SNMP v1 through v3 using SNMP4J. The SNMP4J strategy is enabled by default, but you can go back to the JoeSNMP one if you have a specific need for bug-for-bug compatibility with OpenNMS 1.2′s SNMP behavior.
  • JMX: Support was added for polling and data collection.
  • HTTP Collector: Support was added for data collection via HTTP.
  • NSClient: Support has been added for NSClient (and NSClient++) polling and data collection.
  • Data Export: It is now possible to export RRD data through the web UI.
  • Windows Service Monitoring: Windows services can be monitored through the NSclient support and via a special-purpose poller monitor that uses SNMP.
  • Mail Transport Monitor: It is possible to monitor the complete round-trip availability of a mail system, from sending to checking a mailbox.
  • Page Sequence Monitor: Support has been added for monitoring a complete transaction against a web site, including cookie storage, form submission, and checking the results of the output of a URL.
  • Distributed Monitoring: There is now a distributed monitor that allows you to do service monitoring from multiple locations reported to a single OpenNMS instance.

Thresholding

  • Thresholding for collected performance data is now performed in-line with collection by default. This change makes threshold evaluation virtually instantaneous while drastically lowering the CPU and I/O overhead associated with thresholding. Thresholding for latency data (data from the poller monitors) is still done in the old asynchronous fashion.
  • Absolute Change Thresholds: A new type of threshold useful for monitoring the values of such variables as radio transmitter power (in dB) where a relative change of a given magnitude may not be noteworthy, but an absolute change above some threshold is considered significant.
  • Expression-Based Thresholds: A new type of threshold allowing the user to specify an expression, in standard mathematical terms, involving one or more data source names, operators, and constants.
  • Custom Event UEIs in Thresholds: The types of events generated when thresholds are exceeded or re-armed can now be specified on a per-threshold-definition basis, allowing for much more flexibility in using thresholds as the basis of alarms and notifications.

Notifications

  • Roles: OpenNMS now supports on-call roles. If you have, say, an On-Call role where the users change over time, this feature allows you to schedule them in advance and OpenNMS will manage that schedule for you.
  • Group Duty Schedules: Works like normal duty schedules, except if a Group is listed as a target in a destination path, the duty schedule will apply to the whole group (individual users and roles also in the target are not affected).
  • JavaMail: JavaMail is now the default API used for sending e-mail notifications. This change eliminates the burden of installing, configuring, and troubleshooting a local mail transport agent such as Sendmail or Postfix on the OpenNMS server.
  • Path Outages: A basic path outage capability has been added. This feature addresses the need to suppress notifications for nodes that appear to be down to the OpenNMS system due to a failure in the network path between the nodes and OpenNMS.

Integrations

Web UI

  • Jetty: OpenNMS has a built-in web server (including AJP support), and no longer requires Tomcat for the web UI (although it can still optionally be used)
  • JFreeChart Support: OpenNMS now supports a JFreeChart integration which lets you add charts to the web UI.
  • Zooming: It is now possible to interactively zoom in on graphs.
  • StrafePing: OpenNMS includes an implementation of SmokePing.
  • RSS Feeds: Support has been added for RSS feeds for notifications, outages, alarms, and events.
  • New Look: The OpenNMS web UI got a face lift.
Share on Facebook

OpenNMS 1.6.0 On the Horizon

So I just finished getting OpenNMS 1.5.98 out the door. This is the first release that we’ve left a few (small) known issues in because we’re in hard freeze.

I am so ready for this release to be out; there have been a ton of improvements since 1.2.x and the sooner we can get folks to the current codebase, the better.

Of course, while I was in the process of writing this blog post, Dave found a small but not-insignificant bug that is worth doing another RC for, so here comes 1.5.99! ;)

Share on Facebook