OUCE 2015 – University of Applied Sciences in Fulda


With the help of the faculty for computer science we are happy to present our new venue for the OpenNMS Users Conference Europe 2015 from 28th September until 01. October. The conference is organized by the OpenNMS Foundation Europe e.V. and takes place at the University of Applied Sciences in Fulda.

The Call for Paper ends on 1st August 2015.

Call for Paper Schedule
Conference Board Bursaries

Details can be found on the OUCE 2015 page.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

New COMPASS mobile application

OpenNMS Compass is a modern mobile iOS and Android client for OpenNMS Horizon and OpenNMS Meridian servers.



It provides a simple dashboard for viewing outage and alarm data, node details, and more.

Outage and Alarm Dashboard

At a glance, you can see a summary of any current outages and services with pending problems. One tap will take you to a more detailed view of outages or alarms.

On supported systems*, surveillance categories are also displayed, giving you quick access to availability just like your OpenNMS Horizon or OpenNMS Meridian server UI.



Alarm Details

You can view your current alarms, as well as acknowledge, escalate, and clear them — right from the list, or from the alarm’s details.



Node Details


View detailed information on your nodes, including SNMP attributes, address, availability information*, and outages.

If you are running the latest OpenNMS Horizon or OpenNMS Meridian release*, you can also update the geolocation of a node with the push of a button.


OpenNMS Compass runs on iOS 6 or higher, and Android 4.1 or higher
OpenNMS Compass supports the following OpenNMS server versions:

  • OpenNMS Horizon version 1.12 or higher*
  • OpenNMS Meridian version 2015.1.0 or higher

* Note: Some features are only available on OpenNMS Horizon 15.0.2 or OpenNMS Meridian 2015 or higher.

Frequently Asked Questions

Q: How much does it cost?
A: OpenNMS Compass is free, ad-supported. You can remove the ads for just $1, or they go away automatically if you connect Compass to a Meridian™ server.

Q: I’m getting ‘permission denied’ errors, what should I do?
A: Some versions of OpenNMS are pickier about access and permissions than others. If your version of OpenNMS supports the “mobile” role, it is recommended that you add your user to that role in $OPENNMS_HOME/etc/magic-users.properties.

Q: I already have the old OpenNMS app. Did I waste my money?
A: Nope! Just keep the old OpenNMS app on your device until you have installed Compass. Go to the in-app-purchases screen in Settings, and there is an option to upgrade if the old OpenNMS app is detected. Once you have done so, it is safe to uninstall the old OpenNMS app and enjoy an ad-free Compass!

Getting Help with OpenNMS Compass

There are a couple of ways to get help with OpenNMS Compass:

The OpenNMS Compass Mailing List: An e-mail discussion list for help with and discussion of OpenNMS Compass.

The OpenNMS Issue Tracker: If you find a bug or have a feature request for future OpenNMS Compass releases, please report them to the Compass issue tracker.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 16

We are happy to announce the new stable release of OpenNMS 16 Horizon with codenamed Daredevil. There a lot of enhancements which makes it absolutely worth to install. It is important to know, Capsd is now removed. We also started deprecating LinkD in favour of Enhanced LinkD. If you want to migrate your nodes from Capsd to Provisioning, there is a migration guide using PRIS. The most noticeable ones are:

  • Drools is updated to 6.0.1 Final
  • Trap support for Siemens HiPath 3000/8000
  • Capsd is now completely removed
  • RRD and resource data can now be retrieved via ReST
  • Deprecation of LinkD which means start moving to Enhanced Linkd
  • Migration of the GWT Dashboard to Vaadin
  • Surveillance views can be managed from the WebUI
  • Java 8 support and is now required

The full list of bugfixes and enhancements can be found in our Release Notes. With the resource data available on ReST Jessi White from The OpenNMS Group created a Grafana Plugin for OpenNMS which allows to create performance data dashboards with Grafana from the new measurements API via ReST.

Big thank you to all contributors and happy upgrading.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

OFE goes DevJamming

We offered community members to get a sponsored flight to the University of Minnesota in Twin Cities. Big thank you to The OpenNMS Group, they cover the accommodation for both at the University. We got some proposals and are happy to announce, Umberto Nicoletti from Italy and Marcel Fuhrmann from Germany will join us hack and learn one week with OpenNMS. You may already know them as speaker from OUCE 2013. Umberto did a interesting talk about integrating OpenNMS with configuration management (SaltStack) and Marcel Fuhrmann explained how to do configuration management with help of Redmine. Along with that Marcel helped us organizing and structuring the Wiki and Umberto did also a few interesting side projects around OpenNMS which can you found in his GitHub repository. Looking forward seeing the crowd …

DevJam is coming!

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

OpenNMS @ Bad Voltage

Our source of inspiration Tarus Balog is talking on Bad Voltage. For the ones who don’t know this is Podcast with Jono Bacon, Jeremy Garcia, Stuart Langridge, and Bryan Lunduke, in which they talk about anything that interests them. Technology, Open Source, Politics, Music…anything and everything is up for grabs, complete with reviews and interviews. The 1.5h Podcast 1×39 covers the following topics:

  • What needs to happen so that I can have a drone to deliver my pizza and pick up my shopping? Drawing a line through the technological, regulatory, and philosophical minefield standing between today and Jono’s Glorious Drone-Filled Future (2.40)
  • Tarus Balog speaks about OpenNMS, a network management system for big networks, and some recent changes in the project (27.01)
  • Jono reviews the Go Pro Hero 3+ silver edition extreme sports camera (45.24)
  • Jeremy Clarkson has been fired from Top Gear for hitting a colleague. We draw some fairly obvious parallels between the world of open source and this twin situation of standing up against unacceptable behaviour and whether a project is viable if a leading contributor is dismissed (59.38)

Thank you for listening

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

CLT 2015 – Something about docs

I’ve spend the weekend at CLT 2015 in Chemnitz. It seems this conference became THE™ Linux conference in Germany. The program was quite impressive, 6 parallel tracks filled for two days. It was the first time I had a talk in the publishing track. I decided to give a talk about our documentation project. The idea was to get some feedback and proof our decisions by talking about the ideas, motivations behind rebuilding the OpenNMS documentation. I was surprised about the audience, the room was full. Because there are no recording of the talk here is a short summary and provide some context for the slides you can download from my GitHub repo. I got in contact with a very nice guy who spend time in documentation for the Django project. Browsing through there docs, they really understood, documentation is one of the key components to make an open source project successful. He gave me some valuable hints and pointed me to the Write the Docs conference in Portland and Prag. Maybe one of the readers in the community is interested as well, so maybe we spend some time together. He pointed me also to some interesting information how to deal with multi-language documentation. They use Sphinx but what I’ve seen the concepts work in the same way for AsciiDoc.

First of all I gave a short reminder, source code is not documentation. Many people in Open Source think, publishing the source code prevents them to write documentation – this is wrong. Source code doesn’t tell you anything about motivations, concepts and ideas why you exactly solved the problem this way. Source code is the what and not the why. In real world it is obvious, I can’t pass a bridge build for pedestrians with a car – in software it isn’t – you experience it always if it’s too late. The main idea is to think about why should you write documentation? You want to enable your users to use your software in the most efficient and right way. Documentation has to build a shared understanding between the people writing software and the ones who wants to use it. For Open Source projects documentation is a key value and has a big impact about how many people use it.

There will be ALWAYS™ something to code and so it is for docs. You’ll never finish.

For this reason it make sense to set back and spend some time about thinking, to weave documentation into the development process to increase the quality of documentation. We tried also to find patterns to identify parts to create templates and tried to reuse information and make documentation more efficient. If you develop in an agile environment think about a good written user story is already 50% of documentation when it’s implemented.

We spend last year at DevJam to evaluate some tools. We have found an old DocBook based maven module. Editing DocBook is a pain in the ass, you need a quite expensive tool chain and the barrier is quite high. With AsciiDoc we found the most promising tool chain. Easy as Markdown and very feature rich. The support to get integrated in our Java based Maven build and CI environment works well and we have support in GitHub rendering and viewing the docs just in source.

In hope we can move forward to get our docs improved, it’s not perfect yet but the direction we move seems quite good.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

Dashboard and the surveillance view configuration

The OpenNMS has a Dashboard feature which drives monitoring information through a surveillance view. The surveillance view is a customizable matrix build out of grouped Nodes and shows the status. The matrix view can become quite compact and is used as a driver for getting to monitoring information more quickly. The feature development progress is in JIRA in NMS-7298 and has a feature branch in GitHub with the name jira/NMS-7298.

The feature was originally implemented in GWT. The project started to introduce some new features like the “Ops Board” and the Ops Panel which are also build with Vaadin components. The focus on this project was to cleanup and modernize the code underneath and enable easier iteration on the use case “How we want to have such kind of a dashboard”. The feature is extended with modal popup windows to show alarm, notification and node details without leaving the dashboard. The RRD graphs use the same feature as in Horizon 15 and dynamically resized to the browser width of the Dashboard. It is also now possible to switch between different surveillance views for the Dashboard.

Dashboard refresh

Dashboard refresh

Dashboard Alarm

Dashboard Alarm

Dashboard Notification

Dashboard Notification

For the reason the Dashboard is mainly driven by the “Surveillance View” there is a configuration panel added, which allows to create and modify the surveillance view from the WebUI. The schema of the surveillance-view.xml file is not changed and be used and modified just in the Web UI. The attribute for refresh time in seconds was not used and is now used in the Dashboard and the single Surveillance View. It is now possible to configure different refresh intervals per Surveillance View. The order of columns and rows for the categories can be ordered. The Surveillance View selected as default is the one which is showed first getting to the Dashboard or Surveillance View page.

Manage Surveillance Views

Manage Surveillance Views

Configure Surveillance View

Configure Surveillance View

To allow users or groups a different entry point to the Dashboard, it is possible to map a user or group to a Surveillance View by giving the same name. Instead the default selected Surveillance View the group one is selected. The User name based Surveillance View overwrites the group based Surveillance View.
This feature is marked to be in the coming Horizon 16 release of OpenNMS.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 15.0.1

We are happy to announce OpenNMS 15.0.1 codename silpheed. It is strongly recommended to update. The project is in transition to migrate to Hibernate. We had found an issue where it is possible to have uncleared outages. The outage timeline didn’t showed all outages and is enhanced now to resize automatically (NMS-7438).
You can find the full list of issues and enhancements in the Release notes.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr