Planet OpenNMS

April 07, 2020

OpenNMS Meridian 2019.1.5 (Saturn) Released

Release 2019.1.5 is the sixth release in the Meridian 2019 series.

It fixes a few more security issues, as well as a number of other bugs and a couple of enhancements. Hat tip to Johannes Moritz for the security report.

The codename for 2019.1.5 is Saturn.

Bug
  • SNMP Remove from definitions fails for definitions with profile label (Issue NMS-12413)
  • persisted defaultCalendarReport database reports are broken (Issue NMS-12438)
  • Security issue disclosures, 31 Jan 2020 (Issue NMS-12513)
  • Selecting an Icon on Topology Map breaks the map (Issue NMS-12532)
  • Description: Cannot create monitored-service with JSON via ReST (Issue NMS-12625)
  • Confd download fails silently on Docker install (Issue NMS-12642)
Enhancement
  • Event documentation is missing tokens (Issue NMS-12228)
  • Splitting Docker documentation in Horizon, Minion and Sentinel (Issue NMS-12529)
  • Improve OIA performance when mapping alarms (Issue NMS-12581)
  • Events not balanced across partitions when using opennms-kafka-producer (Issue NMS-12616)

by RangerRick at April 07, 2020 08:06 PM

OpenNMS Meridian 2018.1.17 (Pandemic) Released

Release 2018.1.17 is a small update to 2018.1.16 that fixes another security issue that affects most current OpenNMS releases. Hat tip to Johannes Moritz for reporting this.

The codename for 2018.1.17 is Pandemic.

Bug
  • Security issue disclosures, 31 Jan 2020 (Issue NMS-12513)
  • Drools working memory facts are not restored properly on engine reload (Issue NMS-12586)
  • Confd download fails silently on Docker install (Issue NMS-12642)
Story
  • Backport CircleCI pipeline to foundation-2018 (Issue NMS-12476)

by RangerRick at April 07, 2020 07:20 PM

OpenNMS Meridian 2017.1.22 (meridianu(s) Budense) Released

Release 2017.1.22 is a small update to 2017.1.21 that fixes another security issue that affects most current OpenNMS releases. Hat tip to Johannes Moritz for reporting this.

The codename for 2017.1.22 is meridianu(s) Budense.

Bug

  • Security issue disclosures, 31 Jan 2020 (Issue NMS-12513)
  • Confd download fails silently on Docker install (Issue NMS-12642)

Enhancement

  • Backport CircleCI pipeline to foundation-2017 (Issue NMS-12603)

by RangerRick at April 07, 2020 06:47 PM

April 06, 2020

OpenNMS On the Horizon – April 6th, 2020 – BMP, Kafka, Documentation, CircleCI, Provisiond, Bug Fixes, and More!

It's time for OpenNMS On the Horizon!

In the last week we did more CircleCI infrastructure work, continued to work on BMP features, did more documentation updates, and did a bunch of small feature work and bugfixing.

Github Project Updates

Internals, APIs, and Documentation
  • Dustin, Christian, and Jesse continued their work on improvements to BMP integration.
  • Jesse fixed the minion container to not enable JMS when Kafka is enabled.
  • Bonnie continued her work on improving thresholding documentation.
  • Chandra did more work on the conversion to using protobuf instead of bson for flow payloads.
  • I implemented foundation and release branch merging in CircleCI and turned them off in Bamboo.
  • Jeff disabled logging RTC events by default in Horizon 26 and up.
  • Ronny updated the Horizon and Sentinel CircleCI config to push RC branches.
  • Ronny did more work on updating Helm documentation generation.
  • Ronny updated Minion in smoke tests to run as non-root.
  • Chandra worked on adding tracing support to Provisiond.
  • Patrick worked on a few web UI fixes.
  • Sean worked on updating RPM builds for compatibility.
  • Sean worked on making it possible to ZSTD in Kafka.
Web, ReST, UI, and Helm
  • I fixed documentation generation in OpenNMS.js.
  • I fixed a bug in d3 event handling in the Topology UI.

Calendar of Events

April Releases - April 7th, 2020

The next OpenNMS release day is April 7th, 2020.

Unless we run into major issues, we're hoping to release Horizon 26 in April, which, among other things, includes support for BMP telemetry collection.

There will also be updates to all active Meridian releases.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-8032: Describe Alarm status behavior in user documentation
  • NMS-8546: Event to Notification matching is not documented
  • NMS-9754: RTC subscription events should not be persisted to DB
  • NMS-12426: Add BMP config example and documentation
  • NMS-12513: Security issue disclosures, 31 Jan 2020
  • NMS-12521: Use protobuf instead of bson for encoding/decoding Netflow payloads
  • NMS-12559: Improve parsing of BGP extended communities attribute
  • NMS-12560: Populate path id and labels attributes in unicast prefix messages (OpenBMP integration)
  • NMS-12569: Async DNS resolution for Hostnames in BMP
  • NMS-12617: XSS security issues
  • NMS-12619: sentinel-coordination-zookeeper doesn't start due to missing dependency
  • NMS-12625: Description: Cannot create monitored-service with JSON via ReST
  • NMS-12628: auto-merge foundation branches in CircleCI
  • NMS-12630: Push Minion OCI to DockerHub for release branches
  • NMS-12631: Minion confd template should disable JMS when using Kafka
  • NMS-12635: Restore CAP_NET_RAW capabilities in Minion when running as non-root
  • NMS-12641: Support for more extended community types in BMP
  • NMS-12642: Confd download fails silently on Docker install
  • NMS-12643: Error parsing MP_UNREACH_NLRI attribute
  • NMS-12644: BMP Parser Bulkhead Config does not work

by RangerRick at April 06, 2020 09:43 PM

April 03, 2020

Happy 20th Birthday, OpenNMS!

Earlier this week, OpenNMS turned 20 years old. Although the project began in the summer of 1999, March 30, 2000, marks the day that the OpenNMS Project was registered on Sourceforge and the first time any OpenNMS code was made public. David Hustace, CEO of OpenNMS and Tarus Balog, the company’s COO, share their memories of the past and thoughts about the future.

A Radical Idea in 2000

“The term "open source" was created in 1998 on the heels of the release of the Netscape browser source code, and the OSI [Open Source Initiative] was founded,” says David. “I can't provide an insider perspective on what it was like when OpenNMS first started, but I can tell you that, from an outsider's perspective, it was an extremely radical idea.”

“In 2000, the dot com bubble was subsiding but open source was never going to be considered something to be taken seriously,” he adds. “There was an onslaught of fear, uncertainty and doubt (FUD) coming from a lot of the software industry at the time.”

Network Management Has Changed a Lot

“Back then, most enterprise-level monitoring solutions required expensive hardware from IBM, HP or Sun and the scope was very limited, mainly focused on connectivity and performance network devices such as switches and routers,” says Tarus. “Some vendors were just starting to support Windows, and Linux support was non-existent. Now network monitoring solutions flourish at all levels and on all operating systems.”

David points to virtualization, IoT, and the Cloud, as three of the most significant changes in network management, because of the complexity they add. “Virtualization means monitored entities are now completely abstracted and almost always virtual implementations of their former physical selves; yet they present themselves identically to a monitoring system,” he says. “Moving monitoring applications to the Cloud introduces many application security and networking communications hurdles to crossover, as network and computer technologies still exist in data centers and corporate offices. Monitoring applications that are running in the Cloud require access to those local, on-premise networks to reliably monitor faults and performance; especially when the Cloud applications often require traversing the public Internet. And of course, IoT has changed monitoring with respect to scale. The number of devices on the network needing to be monitored has changed by multiple orders of magnitude due to the compression of technology into almost every aspect of our lives.”

Open Source: from Fringe to Mainstream

“Open source has moved from a fringe idea from a bunch of free software advocates to mainstream acceptance,” says Tarus. “We used to have much more of an ‘evangelical sale’ of OpenNMS in an organization because no one understood it well, or they were frightened by some of the FUD spread by proprietary software vendors. We no longer have that problem, as many large companies have embraced open source from the operating system on up to the software they integrate into their solutions.”

Noteworthy OpenNMS Achievements

“For me it is the fact that we are still around,” says Tarus. “OpenNMS was started by a company called Oculan. Before they went out of business in 2004, they decided to no longer support OpenNMS in May of 2002. While I might have had the option to remain at Oculan, I saw the potential of an open source network monitoring platform that could scale and decided to take a leap of faith and keep the project alive. I was lucky in that I met people like David and was able to convince them of the potential in OpenNMS, enough so that they would quit well-paying jobs to pursue making OpenNMS awesome.”

David laughs. “Twenty years! I thought of this just today … there are potentially users of OpenNMS that are younger than the project. OMG,” he says. “I think it’s significant that we still have our first customer as a customer.”

If You Could Go Back in Time

Both men reflected on what would surprise that younger self if they could go back in time and talk to him.

“That it is worth it,” says Tarus. “Trust me, in the years I’ve worked with OpenNMS there were a lot of times I didn’t think the project was going to make it. It has been the best job I’ve ever had but also the most work.”

“I would be most surprised that this project has these incredibly smart, talented, and wonderful human beings working together and producing an application that is used in production by tens of thousands of very large corporations and most of the biggest, with a combined valuation of trillions of US dollars,” says David.

Where Will OpenNMS be in 20 Years?

In 2000, no one could predict how networking and open source would change and develop. But David and Tarus still have visions for where they want OpenNMS to be 20 years from now. For David, winning the National Medal of Technology and Innovation would be a great honour and achievement.

Tarus’ goal is for OpenNMS to be “the de facto monitoring platform for carriers and large enterprises,” he says.

Personal Stories

Beyond OpenNMS’s success and staying power, it’s the people that have had the greatest impact.

Tarus describes how the company was able to hire one of its contributors, and bring him to the US on an H1B visa. “That eventually turned into a permanent resident card for him and his wife, and his future is now only limited by his imagination,” he says.” If OpenNMS went away tomorrow it would be all worth it for just that one thing, and there are lots of other examples that make all the effort worthwhile.”

Adds David, “OpenNMS and open source has enriched my life by introducing me to, and allowing me to, collaborate and experience life with the most wonderful people in the world.”

by Bonnie at April 03, 2020 05:26 PM

March 30, 2020

It Was Twenty Years Ago Today …

On March 30th, 2000, the OpenNMS Project was registered on Sourceforge. While the project actually started sometime in the summer of 1999, this was the first time OpenNMS code had been made public so we’ve always treated this day as the birth date of the OpenNMS project.

Wow.

OpenNMS Entry on Sourceforge

Now I wasn’t around back then. I didn’t join the project until September of 2001. When I took over the project in May of 2002 I didn’t really think I could keep it alive for twenty years.

Seriously. I wasn’t then nor am I now a Java programmer. I just had a feeling that there was something of value in OpenNMS, something worth saving, and I was willing to give it a shot. Now OpenNMS is considered indispensable at some of the world’s largest companies, and we are undergoing a period of explosive growth and change that should cement the future of OpenNMS for another twenty years.

What really kept OpenNMS alive was its community. In the beginning, when I was working from home using a slow satellite connection, OpenNMS was kept alive by people on the IRC channel, people like DJ and Mike who are still involved in the project today. A year or so later I was able to convince my business partner and good friend David to join me, and together we recruited a real Java programmer in Matt. Matt is no longer involved in the project (people leaving your project is one of the hardest things to get used to in open source) but his contributions in those early days were important. Several years after that we were joined by Ben and Jeff, who are still with us today, and through slow and steady steps the company grew alongside the project. They were followed by even more amazing people that make up the team today (I really want to name every single one of them but I’m afraid I’ll miss one and they’ll be rightfully upset).

I can’t really downplay enough my lack of responsibility for the success of OpenNMS. My only talent is getting amazing people to work with me, and then I just try to remove any obstacles that get in their way. I get some recognition as “The Mouth of OpenNMS” but most of the time I just stand on the shoulders of giants and enjoy the view.

by Tarus at March 30, 2020 09:03 PM

OpenNMS On the Horizon – Minion, Sentinel, Time-Series API, Kafka, Drools, BMP, Helm, CircleCI, and More!

It's time for OpenNMS On the Horizon!

In the last week we did more work on Minion, Sentinel, Kafka, and Drools, as well as the new time-series API, BMP support, the sink API, web UI bugs, and CircleCI.

Also, Happy Birthday to the OpenNMS Project!

SourceForge project started 2000-03-30

Github Project Updates

Internals, APIs, and Documentation
  • Chandra did more work on adding Jolokia to Minion and Sentinel.
  • Patrick's new time-series API was merged to mainline for Horizon 26! (whoo!)
  • Chandra did more work on publishing enriched data to Kafka, as well as fixing some event production balancing issues.
  • Chandra continued his work on moving to protobuf 3 for the sink API.
  • I continued my work on moving Bamboo workflows into CircleCI.
  • Ronny worked on docker container documentation.
  • Chandra worked on an issue with Sentinel Zookeeper integration.
  • Chandra fixed an issue with restoring Drools facts on reload.
  • Dustin added some support for extended community attributes in BGP data.
  • Christian worked on improving unicast support in the BMP integration adapter.
Web, ReST, UI, and Helm
  • Patrick worked on a few other web UI bugs.
  • Jesse fixed an issue with the graph service and nodes without a foreign source or foreign ID.
  • I worked on fixing Helm on Grafana 6.7.

Calendar of Events

April Releases - April 7th, 2020

The next OpenNMS release day is April 7th, 2020.

Unless we run into major issues, we're hoping to release Horizon 26 in April, which includes support for BMP telemetry collection.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-9121: empty Stress Testing section in admin guide
  • NMS-11788: Add SMTP monitor documentation to the Admin Guide
  • NMS-11812: Clarify Basic Installation scenario
  • NMS-12228: Event documentation is missing tokens
  • NMS-12383: Develop Timeseries Integration Layer
  • NMS-12474: dataCollectionSucceeded does event auto-clean
  • NMS-12475: Remove obsolete entry in log4j2.xml
  • NMS-12526: Enrich content of nodeAdded event
  • NMS-12527: Migrate config-tester wiki to the docs
  • NMS-12529: Splitting Docker documentation in Horizon, Minion and Sentinel
  • NMS-12533: Add Jolokia features to Minion & Sentinel
  • NMS-12583: Write enriched flows to Kafka
  • NMS-12586: Drools working memory facts are not restored properly on engine reload
  • NMS-12602: Upgrade Sink API to Proto3
  • NMS-12612: Open Redirect security issues
  • NMS-12615: PR's fail circleci RPM build steps due to missing GPG setup
  • NMS-12616: Events not balanced across partitions when using opennms-kafka-producer
  • NMS-12619: sentinel-coordination-zookeeper doesn't start due to missing dependency
  • NMS-12626: Minion should bind to 0.0.0.0 by default for SNMP traps
  • NMS-12627: Minion Docker image for develop is tagged as 27.0.0-SNAPSHOT instead of bleeding

by RangerRick at March 30, 2020 05:38 PM

March 24, 2020

OpenNMS On the Horizon – March 24th, 2020 – ARM, CircleCI, Documentation, SNMPv3, Time-Series, Flows, and More!

It's time for OpenNMS On the Horizon!

In the last week we wondered... what is time? Does time exist? Is it Monday? Oh, crap, it's Tuesday! I totally forgot to do OOH!

Um.

Anyway... so we worked on ARM support for Docker, CircleCI updates, documentation improvements, BGP, SNMPv3, time-series, flows, and more.

Github Project Updates

Internals, APIs, and Documentation
  • Ronny updated the Minion docker images to use JICMP and JICMP6 rather than JNA.
  • Ronny finished updating the Minion docker images to support ARM builds. Horizon 27 and higher will support x86_64, arm64, and arm/v7. 👏
  • Bonnie worked on updating the documentation to recommend CentOS 8 for Horizon 25+.
  • Sean added ZSTD compression support to our Kafka config.
  • Bonnie added thresholding documentation.
  • Christian added support for parsing BGP capabilities and adding AFI/SAFI statistics as metrics.
  • I got CircleCI builds working on the foundation branches back to foundation-2016.
  • Chandra did more fixes related to SNMPv3 and engine IDs.
  • Chandra did some work on adding Jolokia features to Minion and Sentinel.
  • Chandra worked on updating the sink API to use protobuf 3.
  • Patrick continued his work on the new timeseries API.
  • Chandra worked on writing enriched (classified and tagged) flow data to Kafka.
Web, ReST, UI, and Helm
  • Ron Roskens worked on fixing persisted calendar report display.
  • I added auto-merge support to the Helm CircleCI config.

Calendar of Events

April Releases - April 7th, 2020

The next OpenNMS release day is April 7th, 2020.

Unless we run into major issues, we're hoping to release Horizon 26 in April, which includes support for BMP telemetry collection.

OpenNMS Training - Moonachie, New Jersey - April 27th through May 1st, 2020

The OpenNMS Group still hopes to be offering training at SecureWatch 24 Fusion Center in Moonachie, New Jersey the week of April 27th. 8 seats are available, and the deadline for signing up is April 17th.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-233: auto-merge helm develop -> master in CircleCI
  • MIB-3: running mib2openNMS - Segmentation fault
  • MIB-7: mib2opennms - problem of OID in mask tag
  • MIB-9: mib2opennms : set options -6 and -w as default
  • NMS-2558: Multiple Default SNMP community Strings
  • NMS-2867: OpenNMS MIB: Converting Events to MIB
  • NMS-3045: Create Java SNMP command line utils
  • NMS-3458: Event Configuration error results in success event after reloading
  • NMS-12438: persisted defaultCalendarReport database reports are broken
  • NMS-12476: Backport CircleCI pipeline to foundation-2018
  • NMS-12481: Docker Image Improvements
  • NMS-12482: Reduce Minion docker image size
  • NMS-12483: Publish arm64 and armhf Docker images for Minion
  • NMS-12484: Use jicmp (and jicmp6) by default in Minion Docker images
  • NMS-12553: Add support for per AFI/SAFI statistics
  • NMS-12570: Add support for Local RIB
  • NMS-12571: Parse BGP Capabilities
  • NMS-12574: Apply more sensible defaults to OpenBMP kafka producer
  • NMS-12603: Backport CircleCI pipeline to foundation-2017
  • NMS-12604: Update installation requirements re: CentOS 8
  • NMS-12607: Backport CircleCI pipeline to foundation-2016
  • NMS-12615: PR's fail circleci RPM build steps due to missing GPG setup

by RangerRick at March 24, 2020 03:55 PM

March 19, 2020

I Didn’t Know OpenNMS Could Do That!

Join us April 27 to May 1 for five days of OpenNMS training in Moonachie, New Jersey, with Tarus Balog, COO of The OpenNMS Group.

For 15 years, Tarus has shared his unique perspective and expert tips during an intensive, hands-on training course to help people get the most from OpenNMS and their networks.

Principles Based

Tarus not only covers the basics like installation, events, notifications, alarms, SNMP, data collection, and thresholds, he also discusses the philosophy behind OpenNMS and network management in general.

Students also have the opportunity for hands-on exercises, such as learning how to use the OpenNMS Event Translator to transform and enrich data for custom monitoring. The main course material spans four days with the final, fifth day devoted to real-world use cases from students.

“My students won’t know everything about OpenNMS — we can’t do that in a week,” Tarus says. “But they will understand the capabilities and can figure out from there how to do what they want to do.”

While It’s Magical, It Isn’t Magic

Tarus wants students to understand why OpenNMS works the way it does, and how it can help them with their own unique needs. He cites recent training with one organization, where the group set up an OpenNMS Minion on a device that manages variable message signs (VMS). (You know, those electronic highway signs that display messages like “reduce speed,” “don’t text and drive”, or “zombies ahead”.) In a short time all 80 VMSs were discovered and students could see what had previously been inaccessible to them.

“I love teaching, because it reminds me of how cool OpenNMS is,” says Tarus. “Not just from the ‘aha’ student moments, but from reflecting on how well it does what it does, the full range of its capabilities, and the unique way it solves their issues.”

Register Now

When: April 27 to May 1, 2020, 9 a.m. to 5 p.m.

Where: Fusion Center
70 Moonachie Avenue
Moonachie, NJ 07074

Cost: $2500 per student, lunch included

Only eight spots are available, so register soon. Deadline for registration: April 17, 2020.

Training is sponsored by Securewatch24 and The OpenNMS Group.

by Bonnie at March 19, 2020 02:34 PM

March 16, 2020

OpenNMS On the Horizon – March 16th, 2020 – CircleCI, Time-Series API, Minion and Sentinel, Classification Rules, Prometheus, Docker Updates, Documentation, and More!

It's time for OpenNMS On the Horizon!

Sorry for the delay in getting this out, I was hiding in the Caribbean away from all the toilet paper hoarders.

In the last couple of weeks we worked on CircleCI workflow updates, the new time-series API, improvements to Minion configuration, normalizing our Karaf command-names, CIDR support for classification rules, a Prometheus collector, a bunch of Docker updates, and documentation improvements.

Github Project Updates

Internals, APIs, and Documentation
  • I worked on backporting our CircleCI workflow to foundation-2018 as part of our continuing process to stop using Bamboo internally.
  • Patrick continued his work to create a new API for time-series data.
  • Jesse did more work on the project to normalize all Karaf commands under an opennms: namespace.
  • Matt worked on adding support for using Confd to configure Minions with a yaml file.
  • Dustin continued his work on BMP support.
  • Matt fixed a race condition in Telemetryd logging.
  • Chandra did more work on converting to using protobuf rather than BSON for transporting flow data.
  • Jesse worked on a collector for Prometheus-formatted data.
  • Markus wrapped up adding support for CIDR in classification rule expressions.
  • Chandra worked on fixing a bug in the Karaf command when attempting to remove something from SNMP definitions.
  • Jesse worked on performance improvements to OIA's use of cached alarms.
  • Ronny worked on adding support for publishing arm64/armhf Docker images for Minion.
  • Bonnie did a bunch of updates to the thresholding docs in Horizon, as well as info on making PDF reports from Grafana dashboards.
  • Sean updated our Kafka components dependency to 2.4.0.
  • Chandra made improvements to the node cache used by flow enrichment.
  • Alejandro fixed a bug in the health-check script for Minion and Sentinel Docker images.
Web, ReST, UI, and Helm
  • Ronny and Bonnie did more work on wrapping up CircleCI publishing, building, and documentation for Helm.

Calendar of Events

April Releases - April 7th, 2020

The next OpenNMS release day is April 7th, 2020.

Unless we run into major issues, we're hoping to release Horizon 26 in April, which includes support for BMP telemetry collection.

OpenNMS Training - Moonachie, New Jersey - April 27th through May 1st, 2020

The OpenNMS Group will be offering training at SecureWatch 24 Fusion Center in Moonachie, New Jersey the week of April 27th. 8 seats are available, and the deadline for signing up is April 17th.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • ALEC-83: Deadlock in ALEC causes OpenNMS to hung
  • HELM-206: Document how to use the filter panel
  • HELM-207: Document how to use the entity data-source
  • HELM-214: Publish build artifacts with CircleCI to Cloudsmith
  • HELM-218: Integrate Antora documentation into CircleCI
  • HELM-222: Sign RPM and DEB packages with GPG key
  • HELM-223: Archive old AsciiBinder documentation
  • HELM-227: Some filter could be documented
  • JICMP-24: create CircleCI build for JICMP6
  • NMS-10413: Prefix all shell commands with "opennms"
  • NMS-12413: SNMP Remove from definitions fails for definitions with profile label
  • NMS-12423: Allow CIDR notation in our IP filter implementation
  • NMS-12424: Create BMP Adapter forwarding to OpenBMP
  • NMS-12436: Use Router Id (and maybe AS) to associate node with exporting router's data
  • NMS-12534: Evaluate flow-related Elasticsearch query performance
  • NMS-12565: "No future found for message" warnings in telemetryd log
  • NMS-12573: Refine parameter handling in Adapters
  • NMS-12578: Confd templates for Minion configuration
  • NMS-12580: Improve node cache in flow document enrichment
  • NMS-12581: Improve OIA performance when mapping alarms
  • NMS-12582: Upgrade Kafka components to 2.4.0
  • NMS-12600: The health check script for Minion and Sentinel on Docker Images stopped working

by RangerRick at March 16, 2020 08:23 PM

March 12, 2020

COVID-19

The number of people and countries affected by COVID-19 continues to increase as the disease spreads internationally. Each new reported case presents challenges to the person diagnosed, the surrounding community, and the region reporting the case. We extend our concern and sympathy to those who have been impacted.

Public Health Guidelines

By now, most of us are aware of the guidelines to help prevent the spread of this disease – indeed, things we should always do to minimize illness:

  • Frequently wash hands with soap and water
  • Avoid touching your face
  • Cover coughs and sneezes
  • Clean frequently touched surfaces
  • Stay home when sick

Each affected jurisdiction has its own protocols depending on the state of the outbreak and local public health policies. If you haven’t already, we encourage you to understand and follow those in your area.

The OpenNMS Group Status UPDATE (March 16)

For its part, The OpenNMS Group has implemented travel restrictions for all non-critical business travel (domestic and international). We regret having to postpone our March 23–27, 2020, training in New Jersey, which will be rescheduled at a later date. Current registrants will receive a full refund and notification of the new course when it becomes available.

At this point our employees are not required to work from home, As of March 16, our employees will be working from home, and practicing social distancing when required to be in the office. We at The OpenNMS Group want to assure our customers that the OpenNMS team will continue to provide uninterrupted, high quality service and support.

by Bonnie at March 12, 2020 02:57 PM

March 04, 2020

OpenNMS Horizon 25.2.1 (Gyōza) Released

Release 25.2.1 is the sixth release in the Horizon 25 series.

It contains a number of small improvements as well as a few bug fixes and a security
fix for an HQL injection bug. Hat tip to Johannes Moritz for the security report.

The codename for 25.2.1 is Gyōza.

Bug
  • NMS-12473 - Cannot process SNMPv3 Informs due to random Engine ID associated with users
  • NMS-12505 - api/v2/ifservices endpoint does not expose ID and IpInterface in JSON results
  • NMS-12520 - Downtime model change was not updated in the docs
  • NMS-12531 - Topology Map does not show Geocoordinates anymore
  • NMS-12572 - HQL Injection
Enhancement
  • NMS-12279 - Cleanup Interfaces Tagged for Flows
  • NMS-12422 - Allow multiple IP rules for discontinuous IP ranges for flow classification
  • NMS-12557 - Support signing code in CircleCI

by RangerRick at March 04, 2020 03:53 PM

March 03, 2020

OpenNMS Meridian 2019.1.4 Released

Release 2019.1.4 is the fifth release in the Meridian 2019 series.

It fixes an HQL injection bug, as well as a few other issues. Hat tip to Johannes Moritz for the security report.

The codename for 2019.1.4 is Jupiter.

Bug

  • Cannot process SNMPv3 Informs due to random Engine ID associated with users (Issue NMS-12473)
  • Downtime model change was not updated in the docs (Issue NMS-12520)
  • HQL Injection (Issue NMS-12572)

Enhancement

  • Support signing code in CircleCI (Issue NMS-12557)

by RangerRick at March 03, 2020 10:00 PM

OpenNMS Meridian 2018.1.16 Released

Release 2018.1.16 is a small update to 2018.1.15 that fixes an HQL injection bug, as well as a few other issues. Hat tip to Johannes Moritz for the security report.

The codename for 2018.1.16 is Hurricane.
Bug

  • The Karaf poller:test command is not location aware (Issue NMS-12460)
  • NPE while compiling a MIB (Issue NMS-12472)
  • Cannot process SNMPv3 Informs due to random Engine ID associated with users (Issue NMS-12473)
  • Backport date/time format fixes to Meridian 2018 (Issue NMS-12514)
  • HQL Injection (Issue NMS-12572)

by RangerRick at March 03, 2020 09:40 PM

OpenNMS Meridian 2017.1.21 Released

Release 2017.1.21 is a small update to 2017.1.20 that fixes an HQL injection issue that affects most current OpenNMS releases. Hat tip to Johannes Moritz for reporting this.

The codename for 2017.1.21 is Capitol meridian.

Bug

by RangerRick at March 03, 2020 09:12 PM

OpenNMS On the Horizon – March 3rd, 2020 – Netflow, BMP, Time-Series, Karaf, Helm Docs, Topology, ReST, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on netflow payload processing improvements, BMP support, time-series persistence, Helm documentation, Karaf shell commands, topology UI providers, and new ReST APIs.

Github Project Updates

Internals, APIs, and Documentation
  • Chandra continued his work on using protobuf rather than BSON for netflow payloads.
  • Christian, Dustin, and Jesse did more work on adding BMP support.
  • Patrick continued his work on a new time-series persistence API.
  • Bonnie documented forecast filters for Helm.
  • Chandra added a Karaf shell command for displaying the local SNMP engine ID.
  • Matt fixed a logging race condition in Telemetryd.
Web, ReST, and UI
  • Markus updated the VMware and Enlinkd topology providers to use OIA-enriched vertex metadata.
  • I added /api/v2/ipinterfaces and /api/v2/snmpinterfaces endpoints to the ReST API.

Calendar of Events

March Releases - March 3rd, 2020

The next OpenNMS release day is March 3rd, 2020.

It is expected we'll put out releases on all supported:

  • Horizon 25.2.1
  • Meridian 2017.1.21
  • Meridian 2018.1.16
  • Meridian 2019.1.4
OpenNMS Training - Moonachie, New Jersey - March 23rd through 27th, 2020

The OpenNMS Group will be offering training at SecureWatch 24 Fusion Center in Moonachie, New Jersey the week of March 23rd. 8 seats are available, and the deadline for signing up is March 16th.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • JICMP-23: create CircleCI build for JICMP
  • NMS-11868: WS-Man Integration
  • NMS-12314: Discovery enhancements
  • NMS-12415: Create BMP Adapter for Peer Up / Down Events
  • NMS-12492: Investigate persisting route prefixes learned from BMP in Elasticsearch
  • NMS-12519: Add Netflow 9 generation support to udpgen
  • NMS-12538: Expose OnmsIpInterface, OnmsSnmpInterface, others as top-level resources in REST API
  • NMS-12539: The OpenNMS web UI has encountered an error that it does not know how to handle.
  • NMS-12540: Enable Status Enrichment for existing graph providers
  • NMS-12547: Use ProtoBuf to transport parsed BMP messages
  • NMS-12552: BMP parser is to strict for unknown elements / types
  • NMS-12554: Add basic system test for BMP processing
  • NMS-12557: Support signing code in CircleCI
  • NMS-12564: SystemExecutiveMonitor fails with exit code 6
  • NMS-12572: HQL Injection

by RangerRick at March 03, 2020 05:45 PM

February 27, 2020

Become an OpenNMS Expert: Register Now for Training

POSTPONED

Take your network management to the next level with five days of intensive, interactive, hands-on training. From the basics to advanced topics — including student-specific questions and use cases — Tarus Balog, COO of The OpenNMS Group will teach you how to get the most from OpenNMS and your network. Learn about

  • Installing OpenNMS

  • Setting up notifications, monitoring, and visualizations

  • Advanced topics, troubleshooting, and more

When: March 23–27, 2020, 9 a.m. to 5 p.m.

Where: Fusion Center
70 Moonachie Avenue
Moonachie, NJ 07074

Cost: $2500 per student, lunch included

Only eight spots are available, so register soon. Deadline for registration: March 16, 2020.

Training is sponsored by Securewatch24 and The OpenNMS Group.

by Bonnie at February 27, 2020 04:40 PM

February 24, 2020

OpenNMS On the Horizon – February 24th, 2020 – Time-Series, gRPC, CIDR Rules, Documentation Updates, SNMP Informs, Karaf CLI, Topology UI, ReST Improvements, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on the time-series API, the Karaf CLI, gRPC, CIDR classification rules, SNMP informs, the topology UI, and more.

Github Project Updates

Internals, APIs, and Documentation
  • Patrick continued his work on a new time-series API.
  • Chandra did more work on cleaning up gRPC RPC/sink support.
  • Ronny updated the Docker and config-tester documentation.
  • Markus worked on adding CIDR notation format support to the filter classification rule engine.
  • Bonnie did more cleanup and improvements to documentation formatting.
  • Chandra fixed SNMP inform handling to use a persistent engine ID.
  • Jesse continued to work on refactoring our Karaf CLI commands into a unified opennms: namespace.
  • Chandra worked on switching netflow serialization to use protobuf instead of BSON for performance reasons.
Web, ReST, and UI
  • Markus fixed display of the geolocation info panel in the topology UI.
  • I worked on adding /ipinterfaces and /snmpinterfaces ReST endpoints.

Calendar of Events

March Releases - March 3rd, 2020

The next OpenNMS release day is March 3rd, 2020.

There will be more details as we continue to work on issues, but currently it is expected we'll put out releases on all supported:

  • Horizon 25.2.1
  • Meridian 2016.1.24
  • Meridian 2017.1.21
  • Meridian 2018.1.16
  • Meridian 2019.1.4
OpenNMS Training - Moonachie, New Jersey - March 23rd through 27th, 2020

The OpenNMS Group will be offering training at SecureWatch 24 Fusion Center in Moonachie, New Jersey the week of March 23rd. 8 seats are available, and the deadline for signing up is March 16th.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • ALEC-83: Deadlock in ALEC causes OpenNMS to hung
  • NMS-11840: Docker artifact from build system
  • NMS-11917: Prepare build environment with docker enabled build agent
  • NMS-11926: Name convention for Docker name tag
  • NMS-11931: Develop docker built environment
  • NMS-11956: Docker image build from YUM for CentOS 6.6
  • NMS-11997: Deploy docker image to DockerHub
  • NMS-12024: Trigger docker build from Bamboo develop branch as build stage
  • NMS-12029: Docker image build from YUM for CentOS 6.6 including Postgres 9.3
  • NMS-12372: Add gRPC support for IPC between Minion & OpenNMS
  • NMS-12445: Integrate the new Graph Service API with the OpenNMS Integration API
  • NMS-12473: Cannot process SNMPv3 Informs due to random Engine ID associated with users
  • NMS-12505: api/v2/ifservices endpoint does not expose ID and IpInterface in JSON results
  • NMS-12520: Downtime model change was not updated in the docs
  • NMS-12531: Topology Map does not show Geocoordinates anymore

by RangerRick at February 24, 2020 07:13 PM

February 20, 2020

Join us on Discourse

The OpenNMS Community on Discourse provides a great forum to get help, share ideas, and participate in OpenNMS development. You’ll find about 2,400 searchable posts from the community (including OpenNMS Group staff) on topics like forwarding alarms via Syslog messages and SNMP traps, dealing with Java environments on CentOS and Ubuntu, a discussion of scalable OpenNMS architecture, and announcements about releases and upcoming events.

If you haven’t already, make sure to check out the community. Read, ask questions, share your experiences. Whether you post or just lurk, there’s a wealth of information from users like you that can help you get the most out of your OpenNMS implementation.

We’re especially grateful to the Discourse team who run and maintain the software for us as part of their free hosting for open source projects.

image of mascot holding Discourse logo

by Bonnie at February 20, 2020 06:14 PM

February 18, 2020

OpenNMS On the Horizon – February 18th, 2020 – Flows, Time-Series, Graph API, Karaf, Helm, SNMPv3, Search, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on flows, the time-series and graph APIs, the Karaf CLI, Helm, SNMPv3, web search, and more!

Github Project Updates

Internals, APIs, and Documentation
  • Patrick continued his work on a new time-series API.
  • Christian did more work on flow ingress/egress tagging.
  • Jesse continued working on moving all Karaf commands into an opennms prefix and cleaning up naming.
  • Markus did more work on enhancing flow rule classification configuration.
  • Markus continued his work on integrating the new graph service into OIA.
  • Ronny and I did more work on updating Helm's workflows in CircleCI.
  • Ronny updated the documentation to include the new options for downtime model handling.
  • Marcel made an enhancement to the data provided by a nodeAdded event.
  • Marcel updated the documentation to include information on the config tester.
  • Chandra worked on improving SNMPv3 support to have a persistent engine ID.
Web, ReST, and UI
  • I wrapped up some release changes for Helm.
  • Christian fixed a bug in serializing ID and IP interface in the ifservices ReST endpoint.
  • Markus did some more work on a universal search web interface.

Helm 5

Last week we released Helm 5, our custom plugin for Grafana.

Helm 5 fixes a number of issues, most notably compatibility with newer Grafana releases.
These fixes necessitated dropping compatibility with Grafana versions older than 6.3, so we have bumped the major version of Helm to 5.

Additionally, documentation has been improved and a number of behind-the-scenes changes have been made related to continuous integration and build system.

DockerHub Changes

Ronny pointed out on Discourse that as of Horizon 25, our Docker images are automatically generated from tagged releases in opennms/horizon on DockerHub. Old images that used to reside in the opennms/horizon-core-web DockerHub project have been moved into the new location.

If you have old docker-compose.yml files or K8s deployments that use the old URLs, please migrate them.

Wiki Migration

Marcel has started a project to migrate (and update!) old and outdated wiki pages to Discourse.

If you'd like to help, please check out the discussion and join in the "fun".

Calendar of Events

March Releases - March 3rd, 2020

The next OpenNMS release day is March 3rd, 2020.

There will be more details as we continue to work on issues, but currently it is expected we'll put out releases on all supported:

  • Horizon 25.2.1
  • Meridian 2016.1.24
  • Meridian 2017.1.21
  • Meridian 2018.1.16
  • Meridian 2019.1.4
SCaLE 18x - Pasadena, California - March 5th through 8th, 2020

Tarus Balog will be speaking at SCaLE 18x on alarm correlation (ALEC) and other technologies for large-scale monitoring with OpenNMS.

His presentation is on Saturday the 7th at 4:30pm.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-9495: Use the AsciiBinder framework to content management and publishing
  • NMS-10183: Evaluating Documentation Framework
  • NMS-12279: Cleanup Interfaces Tagged for Flows
  • NMS-12292: Add a "Delete" button on the Node page of the Requisition UI
  • NMS-12422: Allow multiple IP rules for discontinuous IP ranges for flow classification
  • NMS-12447: Remove getVertexType() on GraphInfo
  • NMS-12502: Filter related errors in karaf.log when using new search
  • NMS-12514: Backport date/time format fixes to Meridian 2018
  • NMS-12520: Downtime model change was not updated in the docs

by RangerRick at February 18, 2020 07:06 PM

February 13, 2020

FOSDEM 2020 – So much open source, so little time

Well, the annual pan-European open source jamboree that is FOSDEM, marking its 20th anniversary this year, has come and gone again. OpenNMS developer Ronny Trommer and I were there to sample the mood and fly the OpenNMS flag.

Geeks in Brussels

Each year around 6000 geeks (mostly male and in anoraks) descend on the Université Libre de Bruxelles where over 50 lecture rooms are dedicated to the discussion of all things open source. Subjects range from legal and licencing to open source hardware. Developer rooms are dedicated to specific technical topics such as GIS, Pearl programming, or software-defined networking (SDN). Many of the major open source projects staff a table to promote their work, with the Linux Foundation, Apache, and Eclipse among the biggest presences. The conference is free to attend and run by volunteers.

Geeks heading to the ULB campus.

Ronny and I toured the stands and mostly hung out in the IoT, monitoring, and SDN rooms. We also met up with an old friend of OpenNMS, Patrick Tuit, who was over from Ireland.

This is my fifth FOSDEM, so you might consider me an old hand. The biggest problem with the conference is that there is an awful lot going on and many of the venues are packed and hard to get into. You have to know what you want to see and get there early. My strategy is to stay put once I am in a track and leave only if I need a comfort break :). This means that I end up missing some things but I usually learn something new that I squirrel away for future reference.

IoT and OpenHAB

This year I was after information on IoT. I visited the OpenHAB table and had a long chat with one of the developers to understand the rationale of the project. OpenHAB is targeted at creating a Karaf-based platform for a home hub. It was part of the Eclipse Foundation for a while, but recently left, apparently because they felt the Eclipse process was slowing them down. My main interest in OpenHAB is to understand what, if any, synergy there might be with OpenNMS Minions. For a similar reason I was interested in the Eclipse Foundation's IoT projects, which Bosch is contributing to. Unfortunately, Ubuntu was noticeable by its absence, and I was not able to get a local take on Ubuntu Core's plans for the Raspberry Pi.

Until Next Year

As always, I came away from FOSDEM glad that I went but frustrated at all of the things I was not able to see. A few years ago OpenNMS volunteered a stand at the show, which acted as a magnet for OpenNMS users and I felt gave us a bit more focus. We have also submitted talks in the past to the monitoring track, which helps build mindshare for the project. It may be time to try that again and also to try to organize an OpenNMS training or promotional event before the show. Any feedback or opinions on this would be welcome.

by cgallen at February 13, 2020 08:14 PM

February 10, 2020

OpenNMS On the Horizon – February 10th, 2020 – Helm, BMP, Flows, Karaf, gRPC, Kafka, Graph Service, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on more Helm bugs and documentation, BMP support, flow enhancements, Karaf commands, gRPC and Kafka, graph service improvements, and more!

Github Project Updates

Internals, APIs, and Documentation
  • Bonnie did more work cleaning up and improving Helm documentation.
  • Ronny and Bonnie worked on converting Helm's documentation to publish with Antora.
  • Chandra worked on persisting BMP data to Elasticsearch.
  • Patrick continued his work on a new persistence API.
  • Christian worked on refactoring how interfaces are tagged as having flows.
  • Jesse worked on cleaning up all the Karaf commands to be consistent and under an opennms namespace.
  • Christian added support for forwarding collected BMP telemetry to OpenBMP.
  • Chandra did a bit more work on gRPC IPC support and Kafka topic name cleanups.
  • Markus worked on updating the flow classifications to support multiple IP ranges.
  • Ronny added documentation for the new downtime model delete handling.
Web, ReST, and UI
  • Ronny worked on updating the Helm CircleCI build to do automatic merging.
  • I worked on backporting the date/time angular display fixes to Foundation 2018.
  • Markus did more work on improvements to the new graph service, including integration in OIA.
  • I fixed an issue in Helm where an error would be shown while configuring performance datasource filters.

OpenNMS February Releases

On February 4th we released Meridian 2019.1.3 and Horizon 25.2.0.

Both releases contained a few bug fixes, most notably a fix for some NPEs as well as a performance issue in topology processing.

Additionally, Horizon 25.2.0 included an enhancement to the sink API to persist to disk when the Minion can't reach the broker.

Calendar of Events

SCaLE 18x - Pasadena, California - March 5th through 8th, 2020

Tarus Balog will be speaking at SCaLE 18x on alarm correlation (ALEC) and other technologies for large-scale monitoring with OpenNMS.

His presentation is on Saturday the 7th at 4:30pm.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-208: Error appears when selecting filter type
  • HELM-216: Build docs with CircleCI and publish docs to Netlify
  • HELM-217: Convert docs from Asciibinder to Antora
  • NMS-9811: Thresholds should work without restart when putting nodes into categories
  • NMS-10280: All docs are missing for recent Meridian releases
  • NMS-12428: changing GUI date/timeformat breaks requisition update/import date/time display
  • NMS-12479: Make Kafka RPC topics configurable to use module in topic names
  • NMS-12486: Implement GRPC Server that can route all RPC/Sink messages from OpenNMS to Minion and vice versa

by RangerRick at February 10, 2020 03:29 PM

February 04, 2020

OpenNMS Horizon 25.2.0 (Biscuit Dumpling) Released

Release 25.2.0 is the fifth release in the Horizon 25 series.

It contains a number of bug fixes including a performance fix for topology updating, and an enhancement to the sink API to persist to disk when the Minion can’t reach the broker.

The codename for 25.2.0 is Biscuit Dumpling.

Bug
  • changing GUI date/timeformat breaks requisition update/import date/time display (Issue NMS-12428)
  • Inefficient locking in the TopologyUpdater class (Issue NMS-12443)
  • MIB Compiler fails with Null Pointer Exception (Issue NMS-12459)
  • The Karaf poller:test command is not location aware (Issue NMS-12460)
  • NPE while compiling a MIB (Issue NMS-12472)
Enhancement
  • Sink API: Persistent Off-Heap Storage (Issue NMS-10586)

by RangerRick at February 04, 2020 10:20 PM

OpenNMS Meridian 2019.1.3 (Mars) Released

Release 2019.1.3 is the fourth release in the Meridian 2019 series.

It contains a few bug fixes, most notably a fix for some NPEs as well as a performance issue in topology processing.

The codename for 2019.1.3 is Mars.

Bug
  • changing GUI date/timeformat breaks requisition update/import date/time display (Issue NMS-12428)
  • Inefficient locking in the TopologyUpdater class (Issue NMS-12443)
  • MIB Compiler fails with Null Pointer Exception (Issue NMS-12459)
  • The Karaf poller:test command is not location aware (Issue NMS-12460)
  • NPE while compiling a MIB (Issue NMS-12472)

by RangerRick at February 04, 2020 08:17 PM

February 03, 2020

OpenNMS On the Horizon – February 3rd, 2019 – Helm, InfluxDB, Kafka RPC, and More!

It's time for OpenNMS On the Horizon!

In the last week we cleaned up Helm compatibility, worked on InfluxDB support, continued to improve Kafka RPC, and more.

Github Project Updates

Internals, APIs, and Documentation
  • Bonnie did more work on cleaning up documentation in various places.
  • Markus continued to work on integrating the new graph service API into OIA.
  • Patrick worked on an InfluxDB implementation for the new time-series API.
  • Chandra continued his work making Kafka RPC topics more configurable.
  • Ronny worked on moving some Bamboo merge and documentation actions to CircleCI.
  • Markus did more work on fixing a performance issue in the ALEC topology updater.
Web, ReST, and UI
  • I wrapped up the code for my fix for parsing format strings in AngularJS.
  • I fixed a number of Helm bugs including Grafana 6.5 and 6.6 support.

Calendar of Events

February Releases - February 4th, 2020

The next OpenNMS release day is February 4th, 2020.

There will be more details as we continue to work on issues, but currently it is expected we'll put out the following releases:

  • Horizon 25.1.3
  • Meridian 2019.1.3

SCaLE 18x - Pasadena, California - March 5th through 8th, 2020

Tarus Balog will be speaking at SCaLE 18x on alarm correlation (ALEC) and other technologies for large-scale monitoring with OpenNMS.

His presentation is on Saturday the 7th at 4:30pm.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-196: Alarm table rendering failures with Grafana 6.5.2
  • HELM-205: Document how to use template variables and node label transforms
  • HELM-210: Documentation doesn't show latest release
  • HELM-211: Grafana dependency should be updated and should be more specific
  • HELM-212: number (count) columns render wrong in Grafana 6.5 and 6.6
  • HELM-219: Update CircleCI build pipeline from 2.0 to 2.1
  • NMS-12443: Inefficient locking in the TopologyUpdater class
  • NMS-12453: Expose status information when fetching a graph view

by RangerRick at February 03, 2020 05:41 PM

January 27, 2020

OpenNMS On the Horizon – January 27th, 2020 – Bug Fixing, Graph Service, Off-Heap Storage, Documentation, and More!

OpenNMS On the Horizon

It's time for OpenNMS On the Horizon!

In the last couple of weeks we merged a number of new features that have been in the works for a while (graph API, off-heap storage), fixed a bunch of bugs, and started on reworking some documentation.

Github Project Updates
  • Internals, APIs, and Documentation

    • Markus enhanced the new graph API to expose status information.
    • Patrick continued his work refactoring the time-series APIs.
    • Chandra continued his work on adding gRPC support for the Minion.
    • Matt fixed another bug in the dreaded syslog date parsing algorithm.
    • Bonnie made a bunch of improvements to the Helm documentation.
    • Marcel fixed a bug where datacollection failures could be masked by auto-clean.
    • Chandra fixed some issues with using the default foreign source during discovery.
    • Christian worked on normalizing our Karaf shell commands.
    • Markus worked on fixing a performance issue with locking in ALEC topology updates.
    • Pierre, Jesse, and I worked on fixing build issues with Maven Central blocking non-HTTPS connections.
    • Dustin continued his work on BMP support in Telemetryd.
    • Pierre converted events internally to be immutable.
    • Markus started adding graph API support to OIA.
    • Chandra worked on making Kafka RPC topics more configurable.
    • Matt finished his new implementation of off-heap storage for the sink API.
  • Web, ReST, and UI

    • Qauseen added pagination to the node search modal in Helm.
    • Qauseen fixed a performance issue where the Helm panel would refresh for each alarm being cleared, rather than when it finished.
    • Markus and I worked on fixing custom date formatting in AngularJS.
    • Christian fixed an NPE in the MIB compiler.
Calendar of Events
  • February Releases - February 4th, 2020

    The next OpenNMS release day is February 4th, 2020.

    There will be more details as we continue to work on issues, but currently it is expected we'll put out the following releases:

    • Horizon 25.1.3
    • Meridian 2019.1.3

  • FOSDEM 2020 - Brussels, Belgium - Feb 1st and 2nd, 2020

    Ronny Trommer will be attending FOSDEM 2020. If you want to meet and talk, contact him on Twitter, Discourse, or email him at ronny[eth]opennms-dot-com.

  • SCaLE 18x - Pasadena, California - March 5th through 8th, 2020

    Tarus Balog will be speaking at SCaLE 18x on alarm correlation (ALEC) and other technologies for large-scale monitoring with OpenNMS.
    His presentation is on Saturday the 7th at 4:30pm.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH
  • HELM-64: Node search allows only to select the first 25 nodes
  • HELM-201: Panel Refreshes After Each Request When Clearing Multiple Alarms
  • HELM-204: Document how to use filters for forecasting metrics
  • NMS-10586: Sink API: Persistent Off-Heap Storage
  • NMS-10720: Make Events immutable (avoid CMEs and fix non-deterministic behavior)
  • NMS-12086: Provide a better graph service with an actual API/Model and better import/export/integration capabilities
  • NMS-12411: Discovery and foreignSource service detection get in the way
  • NMS-12459: MIB Compiler fails with Null Pointer Exception
  • NMS-12460: The Karaf poller:test command is not location aware

by RangerRick at January 27, 2020 09:24 PM

January 23, 2020

Once Again Into the Breach – Back with Apple

After almost a decade since my divorce from Apple, I find myself back with the brand, and it is all due to the stupid watch.

TL;DR: As a proponent of free software, I grouse at the “walled garden” approach Apple takes with its products, but after a long time of not using their products I find myself back in, mainly because free software missed the boat on mobile.

Back in 2011, I stopped using Apple products. This was for a variety of reasons, and for the most part I found that I could do quite well with open source alternatives.

My operating system of choice became Linux Mint. The desktop environment, Cinnamon, allowed me to get things done without getting in the way, and the Ubuntu base allowed me to easily interact with all my hardware. I got rid of my iMac and bought a workstation from System 76, and for a time things were good.

I sold my iPhone and bought an Android phone which was easier to interact with using Linux. While I didn’t have quite all of the functionality I had before, I had more than enough to do the things I needed to do.

But then I started to have issues with the privacy of my Android phone. I came across a page which displayed all of the data Google was collecting on me, which included every call, every text and every application I opened and how long I used it. Plus the stock Google phones started to ship with all of the Google Apps, many of which I didn’t use and they just took up space. While the base operating system of Android, the Android Open Source Project (AOSP), is open source, much of the software on a stock Android phone is very proprietary, with questionable motives behind gathering all of that data.

Then I started playing with different Android operating systems known as “Custom ROMs”. Since I was frequently installing the operating system on my phone I finally figured out that when Google asks “Would you like to improve your Android experience?”, and you say “yes”, that is when they start the heavy data collection. Opt-out and the phone still works, but even basic functionality such as storing your recent location searches in Google Maps goes away. Want to be able to go to a previous destination with one click? Give them all yer infos.

The Custom ROM world is a little odd. While there is nothing wrong with using software projects run by hobbyists, the level of support can be spotty at best. ROMs that at one time were heavily supported can quickly go quiet as maintainers get other interests or other handsets. For a long time I used OmniROM with a minimal install of Google Apps (with the “do not improve my Android experience” option) and it even worked with my Android Wear smartwatch from LG.

I really liked my smartwatch. It reminded me of when we started using two monitors with our desktops. Having things like notifications show up on my wrist was a lot easier to deal with than having to pull out and unlock my phone.

But all good things must come to an end. When Android Wear 2.0 came out they nerfed a lot of the functionality, requiring Android Assistant for even the most basic tasks (which of course requires the “improved” Android experience). I contacted LG and it wasn’t possible to downgrade, so I stopped wearing the watch.

Things got a little better when I discovered the CopperheadOS project. This was an effort out of Canada to create a highly secure handset based on AOSP. It was not possible (or at least very difficult) to install Google Apps on the device, so I ended up using free software from the F-Droid repository. For those times when I really needed a proprietary app I carried a second phone running stock Android. Clunky, I know, but I made it work.

Then CopperheadOS somewhat imploded. The technical lead on the project grew unhappy with the direction it was going and left in a dramatic fashion. I tried to explore other ROMs after that, but grew frustrated in that they didn’t “just work” like Copperhead did.

So I bought an iPhone X.

Apple had started to position themselves as a privacy focused company. While they still don’t encrypt information in iCloud, I use iCloud minimally so it isn’t that important to me. It didn’t take me too long to get used to iOS again, and I got an Apple Watch 3 to replace my no longer used Android Wear watch.

This was about the time the GDPR was passed in the EU, and in order to meet the disclosure requirements Apple set up a website where you could request all of the personal data they collected on you. Now I have been a modern Apple user since February of 2003 when I ordered a 12-inch Powerbook, so I expected it to be quite large.

It was 5MB, compressed.

The majority of that was a big JSON file with my health data collected from the watch. While I’m not happy that this data could be made available to third parties as it isn’t encrypted, it is a compromise I’m willing to make in order to have some health data. Now that Fitbit is owned by Google I feel way more secure with Apple holding on to it (plus I have no current plans to commit a murder).

The Apple Watch also supports contactless payments through Apple Pay. I was surprised at how addicted I became to the ease of paying for things with the watch. I was buying some medication for my dog when I noticed their unit took Apple Pay, and the vet came by and asked “Did you just Star Trek my cash register?”.

Heh.

For many months I pretty much got by with using my iPhone and Apple Watch while still using open source for everything else. Then in July of last year I was involved in a bad car accident.

In kind of an ironic twist, at the time of the accident I was back to carrying two phones. The GrapheneOS project was created by one of the founders of Copperhead and I was once again thinking of ditching my iPhone.

I spent 33 nights in the hospital, and during that time I grew very attached to my iPhone and Watch. Since I was in a C-collar it made using a laptop difficult, so I ended up interacting with the outside world via my phone. Since I slept off and on most of the day, it was nice to get alerts on my watch that I could examine with a glance and either deal with or ignore and go back to sleep.

This level of integration made me wonder how things worked now on OSX, so I started playing with a Macbook we had in the office. I liked it so much I bought an iMac, and now I’m pretty much neck deep back in the Apple ecosystem.

The first thing I discovered is that there is a ton of open source software available on OSX, and I mainly access it through the Homebrew project. For example, I recently needed the Linux “watch” command and it wasn’t available on OSX. I simply typed “brew install watch” and had it within seconds.

The next major thing that changed for me was how integrated all my devices became. I was used to my Linux desktop not interacting with my phone, or my Kodi media server being separate from my smartwatch. I didn’t realize how convenient a higher level of integration could be.

For example, for Christmas I got an Apple TV. Last night we were watching Netflix through that device and when I picked up my iPhone I noticed that I could control the playback and see information such as time elapsed and time remaining for the program. This happened automatically without the need for me to configure anything. Also, if I have to enter in text, etc. on the Apple TV, I can use the iPhone as a keyboard.

I’ve even started to get into a little bit of home automation. I bought a “smart” outlet controller that works with Homekit. Now I don’t have the “Internet of Things”, instead I have the “LAN of Things” as I block Internet access for most of my IoT-type things such as cameras. Since the Apple TV acts as a hub I can still remotely control my devices even though I can’t reach them via the Internet. All of the interaction occurs through my iCloud account, so I don’t even have to poke a hole in my firewall. I can control this device from any of my computers, my iPhone or even my watch.

It’s pretty cool.

It really sucks that the free and open source community missed the boat on mobile. The flagship mobile open source project is AOSP, and that it heavily controlled by Google. While some brave projects are producing Linux-based phones, they have a long way to go to catch up with the two main consumer options: Apple and Google. For my piece of mind I’m going with Apple.

There are a couple of things Tim Cook could do to ease my conscience about my use of Apple products. The first would be to allow us the option of having greater control of the software we install on iOS. I would like to be able to install software outside of the App Store without having to jailbreak my device. The second would be to enable encryption on all the data stored in iCloud so that it can’t be accessed by any other party than the account holder. If they are truly serious about privacy it is the logical next step. I would assume the pressure from the government will be great to prevent that, but no other company is in a better position to defy them and do it anyway.

by Tarus at January 23, 2020 05:43 PM

January 13, 2020

OpenNMS On the Horizon – January 13th, 2020 – Refactoring, gRPC, Helm, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on a bunch of refactoring, plus gRPC support, Helm, and some other fixes.

Github Project Updates

  • Internals, APIs, and Documentation

    • I did more work on moving CI tasks to CircleCI and CloudSmith.
    • Chandra did more work wrapping up gRPC IPC support for Minion <-> OpenNMS communication.
    • Patrick continued his work on refactoring/cleaning up the time-series APIs.
    • Pierre worked on making events immutable internally, which should clean up a whole bunch of potentially undefined behaviors in OpenNMS.
  • Web, ReST, and UI

    • Qauseen worked on some enhancements and cleanup in Helm including fixes to actions and pagination.
    • Jesse fixed an issue with alarm table sorting and alarm details in Helm.

January Releases: Meridian 2018.1.15, Meridian 2019.1.2, and Horizon 25.1.2

January saw the release of 3 point updates for OpenNMS Meridian and Horizon.

Meridian 2018.1.15 was a very small release with a topology UI fix and a fix to some debug logging.

Meridian 2019.1.2 and Horizon 25.1.2, on the other hand, contained a ton of fixes to Alarmd processing, flows, and more.

For a complete list of changes, see the release notes:

Calendar of Events

  • February Releases - February 4th, 2020

    The next OpenNMS release day is February 4th, 2020.

    There will be more details as we continue to work on issues, but currently it is expected we'll put out the following releases:

    • Horizon 25.1.3
    • Meridian 2019.1.3

  • SCaLE 18x - Pasadena, California - March 5th through 8th, 2020

    Tarus Balog will be speaking at SCaLE 18x on alarm correlation (ALEC) and other technologies for large-scale monitoring with OpenNMS.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-139: Alarm Table page has a number of bugs
  • HELM-202: Alarms details modal shows wrong alarm when table is sorted
  • NMS-12448: Avoid rebuilding the graph view when enriching
  • NMS-12467: CircleCI packages should have branch number and incrementing build
  • NMS-12471: DatacollectionFailed event definitions are located in wrong file

by RangerRick at January 13, 2020 05:42 PM

January 07, 2020

OpenNMS Horizon 25.1.2 (Pierogi) Released

Release 25.1.2 is the fourth release in the Horizon 25 series.

It contains a number of alarm classification bug fixes and performance improvements, flow enhancements, and more.

The codename for 25.1.2 is Pierogi.

Bug
  • possible issue in JCIFS Monitor - contiously increase of threads - finally heap dump (Issue NMS-12407)
  • Wrong links in the Help/Support page (Issue NMS-12418)
  • Classification Engine reload causes OOM when defining a bunch of rules (Issue NMS-12429)
  • TCP Listeners are broken (Issue NMS-12430)
  • Cannot define a specific layer in topology app URL (Issue NMS-12431)
  • Classification UI: Error responses are not shown properly (Issue NMS-12432)
  • Classification Engine: The end of the range is excluded, which is not intuitive (Issue NMS-12433)
  • Ticket-creating automations are incorrectly enabled by default (Issue NMS-12439)
  • Enable downtime model-based node deletion to happen when unmanaged interfaces exist (Issue NMS-12442)
  • Improve alarmd Drools engine performance by using STREAM mode (Issue NMS-12455)
Enhancement
  • Refactoring of the Cassandra installation instructions (Issue NMS-12397)
  • SNMP detector should use snmp profiles (Issue NMS-12406)
  • Allow telemetry flows to balance across Kafka partitions (Issue NMS-12427)
  • Add system test for IpfixTcpParser (Issue NMS-12434)
  • Associate exporter node using Observation Domain Id (Issue NMS-12435)

by RangerRick at January 07, 2020 07:43 PM

OpenNMS Meridian 2019.1.2 (Earth) Released

Release 2019.1.2 is the third release in the Meridian 2019 series.

It contains a number of alarm classification bug fixes and performance improvements, flow enhancements, and more.

The codename for 2019.1.2 is Earth.

Bug
  • possible issue in JCIFS Monitor - contiously increase of threads - finally heap dump (Issue NMS-12407)
  • Wrong links in the Help/Support page (Issue NMS-12418)
  • Classification Engine reload causes OOM when defining a bunch of rules (Issue NMS-12429)
  • Cannot define a specific layer in topology app URL (Issue NMS-12431)
  • Classification UI: Error responses are not shown properly (Issue NMS-12432)
  • Classification Engine: The end of the range is excluded, which is not intuitive (Issue NMS-12433)
  • Ticket-creating automations are incorrectly enabled by default (Issue NMS-12439)
  • Enable downtime model-based node deletion to happen when unmanaged interfaces exist (Issue NMS-12442)
  • Improve alarmd Drools engine performance by using STREAM mode (Issue NMS-12455)
Enhancement
  • Refactoring of the Cassandra installation instructions (Issue NMS-12397)
  • Allow telemetry flows to balance across Kafka partitions (Issue NMS-12427)
  • Add system test for IpfixTcpParser (Issue NMS-12434)
  • Associate exporter node using Observation Domain Id (Issue NMS-12435)

by RangerRick at January 07, 2020 05:15 PM

OpenNMS Meridian 2018.1.15 (Cyclone) Released

Release 2018.1.15 is a tiny update containing a logging fix in Provisiond and an update to allow for choosing a layer when linking to the topology UI.

The codename for 2018.1.15 is Cyclone.

Bug
  • Cannot define a specific layer in topology app URL (Issue NMS-12431)

by RangerRick at January 07, 2020 05:12 PM

January 06, 2020

OpenNMS On the Horizon – January 6th, 2020 – Graph API, SNMP Profiles, Package Repositories, Documentation, and More!

It's time for OpenNMS On the Horizon!

Since before our Holiday break we continued to work on graph and SNMP enhancements, moving packages to a (hopefully) faster and easier-to-manage cloud service, and updated documentation.

Github Project Updates

  • Internals, APIs, and Documentation

    • Markus did more work on optimizing and improving the new graph service API.
    • Chandra continued his work on updating the SNMP detector to support SNMP config profiles.
    • Ronny did more work on the Cassandra installation docs.
    • Jeff fixed the default alarmd drools rules to skip ticket creation to match the old behavior.
    • I worked on publishing our RPM and Debian packages to CloudSmith.
    • Patrick continued his work refactoring our existing time-series persistence APIs.
    • Bonnie worked on improving the Helm documentation.
  • Web, ReST, and UI

    • Jesse worked on enhancing the Alarm API to retrieve historical alarms from Elasticsearch.

Calendar of Events

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-195: "Canceled:Query Changed while running" when clearing multiple alarms
  • NMS-12397: Refactoring of the Cassandra installation instructions
  • NMS-12406: SNMP detector should use snmp profiles
  • NMS-12439: Ticket-creating automations are incorrectly enabled by default
  • NMS-12442: Enable downtime model-based node deletion to happen when unmanaged interfaces exist
  • NMS-12454: Make it easy to download Debian/RPM artifacts from CircleCI
  • NMS-12455: Improve alarmd Drools engine performance by using STREAM mode
  • NMS-12463: RRDTool 1.7.0 permission bug when running as non-root
  • NMS-12464: Deploy RPMs and Debian Packages to CloudSmith

by RangerRick at January 06, 2020 04:32 PM

December 16, 2019

OpenNMS On the Horizon – December 16th, 2019 – Documentation, Bug Fixes, Topology and Classification UI, and More!

It's time for OpenNMS On the Horizon!

In the last week we updated documentation, fixed a number of important bugs, continued to work on topology and classification UI improvements, and more.

Github Project Updates

  • Internals, APIs, and Documentation

    • Ronny worked with Alejandro and Jesse to improve our Newts installation guide to follow more best practice with Schema installation and we have stopped maintaining our own Cassandra installation instructions.
    • Patrick continued his work on refactoring and evaluating our time series APIs.
    • Markus worked on documentation for the new graph service.
    • Dustin fixed some issues with dropped packets on the telemetryd listeners.
    • Jesse fixed some issues with exception handling in OIA.
    • Markus made improvements to the flow classification rule engine to reduce memory usage and to fix port range handling.
    • Chandra updated the SNMP detector to support SNMP profiles.
    • Christian fixed some issues with associating flows with nodes behind NAT.
    • Jesse did more work on the changes to allow flows to balance across Kafka partitions.
    • Markus worked on optimizations in graph view enrichment.
    • I worked on adding support for deleting nodes triggered by the downtime model if only unmanaged interfaces remain.
    • Jesse updated Alarmd processing to use Drools streaming again now that they have fixed upstream bugs.
  • Web, ReST, and UI

    • Markus did more work on adding support for choosing a layer in the topology UI in the URL.
    • Markus fixed the classification UI to report better error messages.
    • Antonio continued his work on enhancements to the topology link provider.

Calendar of Events

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • ALEC-65: Model inventory for BGP peers
  • ALEC-82: OpenNMS Direct Inventory Datasource Peformance Issues
  • NMS-11847: Add support to use Apache Kafka as Messaging Broker with Docker Image
  • NMS-11934: As an Operator I want to configure the message producer to use Kafka so I can use my existing scalable Kafka infrastructure with Minions
  • NMS-11973: As an Operator I want to configure the message consumer to use Kafka so I can use my existing scalable Kafka infrastructure with Horizon
  • NMS-12407: possible issue in JCIFS Monitor - contiously increase of threads - finally heap dump
  • NMS-12418: Wrong links in the Help/Support page
  • NMS-12427: Allow telemetry flows to balance across Kafka partitions
  • NMS-12430: TCP Listeners are broken
  • NMS-12431: Cannot define a specific layer in topology app URL
  • NMS-12432: Classification UI: Error responses are not shown properly
  • NMS-12433: Classification Engine: The end of the range is excluded, which is not intuitive
  • NMS-12434: Add system test for IpfixTcpParser
  • NMS-12435: Associate exporter node using Observation Domain Id
  • NMS-12441: Provide basic development documentation

by RangerRick at December 16, 2019 07:32 PM

December 09, 2019

OpenNMS On the Horizon – December 9th, 2019 – BMP, Graph Service, Time-Series APIs, Bug Fixes, and More!

It's time for OpenNMS On the Horizon!

In the last week we continued to work on BMP and improving graph and time-series APIs, as well as other bug fixing and enhancements.

Github Project Updates

  • Internals, APIs, and Documentation

    • Dustin continued to work on adding BMP support.
    • I fixed a bug where the ElasticSearch forwarder could modify events before they're passed on to other subsystems.
    • Chandra fixed a bug in opennms-snmp:remove-from-definition
    • Markus continued his work enhancing the new graph API.
    • Christian fixed an issue with leaked threads in JCIFS.
    • Antonio and Markus did more work on improvements to topology link provider(s).
    • Sean Torres worked on fixes to allow flows to balance across Kafka partitions.
    • Christian fixed processing of filter rules in poller-configuration.xml.
    • Patrick continued his work evaluating how to rework our time-series APIs.
    • Jeff worked on an absolute-value handler for the JRobin spike hunter.
    • Markus fixed an issue with classification rule definitions that could cause OOM.
    • Chandra worked on adding gRPC support for IPC between Minion and OpenNMS.
  • Web, ReST, and UI

    • Markus updated the topology UI to allow choosing a layer with a URL parameter.

December Horizon and Meridian Releases

In December we released updated versions of Horizon 25, Meridian 2018, and Meridian 2019.

Meridian 2018.1.14 was primarily a small bug fix release. Meridian 2019.1.1 and Horizon 25.1.1 both had a larger number of bug fixes mostly related to alarm and event processing and potential resource leaks, and a few other enhancements.

Calendar of Events

  • January Releases - January 7th, 2020

    The next OpenNMS release day is January 7th, 2020.

    So far we expect to be putting out the following releases:

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-12358: Create BMP listener and parser for telemetryd
  • NMS-12390: Elasticsearch event forwarder manipulates in-flight event
  • NMS-12400: Invalid poller filter rules can break service web UI page
  • NMS-12414: Create BMP Adapter for Telemetry
  • NMS-12415: Create BMP Adapter for Peer Up / Down Events
  • NMS-12425: Create graph definitions for BMP statistics
  • NMS-12429: Classification Engine reload causes OOM when defining a bunch of rules

by RangerRick at December 09, 2019 06:24 PM

December 03, 2019

OpenNMS Horizon 25.1.1 (Bánh bột lọc) Released

Release 25.1.1 is the third release in the Horizon 25 series.

It contains a number of bug fixes mostly related to alarm and event processing and potential resource leaks, as well as provisioning enhancements to SNMP profiles.

The codename for 25.1.1 is Bánh bột lọc.

Bug
  • Readiness probe with Minion in Kubernetes with health:check does not work (Issue NMS-12120)
  • AlarmLifecycleListenerManagerIT and AlarmdIT flapping (Issue NMS-12309)
  • Strange behavior on used threads and file descriptors on Minion (Issue NMS-12366)
  • Upstream Drools Bug: From with modify fires unexpected rule (Issue NMS-12367)
  • Build failure during release for 25.1.0 in CircleCI (Issue NMS-12380)
  • Discovery does not honor exclude-range inside a definition (Issue NMS-12385)
  • Discovery exclude-range is not location-aware (Issue NMS-12386)
  • Update OpenJDK 11.0.4 to 11.0.5 (Issue NMS-12387)
  • Elasticsearch event forwarder manipulates in-flight event (Issue NMS-12390)
  • send-event.pl is broken after OpenNMS 25.1.0 update (Issue NMS-12392)
  • SNMP profile fitting is not triggered in some cases when MINION is involved (Issue NMS-12399)
  • Alarmd fails intermittently and OOMs (Issue NMS-12412)
  • SNMP Remove from definitions fails for definitions with profile label (Issue NMS-12413)
Enhancement
  • Migrate guide to run with Docker from GitHub repo to Installation guide (Issue NMS-12375)
  • Enhance new snmp profiles to allow fitting to nodes inside requisitions without SNMP service associated to any IPs configured (Issue NMS-12396)
  • Use OpenJDK 8 JDK for build environment (Issue NMS-12398)

by RangerRick at December 03, 2019 10:10 PM

OpenNMS Meridian 2019.1.1 (Venus) Released

Release 2019.1.1 is the second release in the Meridian 2019 series.

It contains a number of bug fixes mostly related to alarm and event processing and potential resource leaks, as well as provisioning enhancements to SNMP profiles.

The codename for 2019.1.1 is Venus.

Bug
  • Readiness probe with Minion in Kubernetes with health:check does not work (Issue NMS-12120)
  • Cannot use poller:poll karaf command with WsManMonitor through Minions (Issue NMS-12365)
  • Strange behavior on used threads and file descriptors on Minion (Issue NMS-12366)
  • Upstream Drools Bug: From with modify fires unexpected rule (Issue NMS-12367)
  • "Page Not Found" in alarm-list when choosing number of alarms in dropdown-list (Issue NMS-12379)
  • Build failure during release for 25.1.0 in CircleCI (Issue NMS-12380)
  • backport missing patches from 25.1.0 to foundation-2019 (Issue NMS-12384)
  • Discovery does not honor exclude-range inside a definition (Issue NMS-12385)
  • Discovery exclude-range is not location-aware (Issue NMS-12386)
  • Update OpenJDK 11.0.4 to 11.0.5 (Issue NMS-12387)
  • Elasticsearch event forwarder manipulates in-flight event (Issue NMS-12390)
  • send-event.pl is broken after OpenNMS 25.1.0 update (Issue NMS-12392)
  • SNMP profile fitting is not triggered in some cases when MINION is involved (Issue NMS-12399)
  • Alarmd fails intermittently and OOMs (Issue NMS-12412)
  • SNMP Remove from definitions fails for definitions with profile label (Issue NMS-12413)
Enhancement
  • Create a step-by-step guide how to setup Kafka for Minions (Issue NMS-12368)
  • Enhance new snmp profiles to allow fitting to nodes inside requisitions without SNMP service associated to any IPs configured (Issue NMS-12396)

by RangerRick at December 03, 2019 10:01 PM

OpenNMS Meridian 2018.1.14 (Earthquake) Released

Release 2018.1.14 is a small update to 2018.1.13 that fixes a few bugs including a fix to syslog date parsing, Drools fixes, and a few other changes.

The codename for 2018.1.14 is Earthquake.

Bug
  • Syslog incorrect dates being parsed into database (Issue NMS-10605)
  • Cannot use poller:poll karaf command with WsManMonitor through Minions (Issue NMS-12365)
  • Upstream Drools Bug: From with modify fires unexpected rule (Issue NMS-12367)
  • "Page Not Found" in alarm-list when choosing number of alarms in dropdown-list (Issue NMS-12379)
  • Elasticsearch event forwarder manipulates in-flight event (Issue NMS-12390)

by RangerRick at December 03, 2019 08:46 PM

December 02, 2019

OpenNMS On the Horizon – December 2nd, 2019 – SNMP, Time Series Data, ALEC, BMP in Telemetryd, Linkd, and More!

It's time for OpenNMS On the Horizon!

In the last week we worked on SNMP profile matching, time series APIs, ALEC improvements, BMP in Telemetryd, the Linkd topology provider, and more!

Github Project Updates

  • Internals, APIs, and Documentation

    • Chandra continued to work on wrapping up improvements and fixes to profile fitting when provisioning.
    • Patrick did more work on evaluating refactoring our time series APIs.
    • Chandra worked on fixing exclude ranges inside discovery definitions.
    • Markus continued his work on improvements to the graph services API.
    • Jesse updated the ALEC API to use an IP->node cache.
    • Christian worked on fixing bugs in filter processing in poller-configuration.xml.
    • Chandra worked on fixing some issues with handling foreign sources in new suspect scans.
    • Chandra fixed a bug in the opennms-snmp:remove-from-definition Karaf command.
    • Dustin did more work on implementing BMP support in Telemetryd.
    • Antonio worked on improvements to the Linkd topology provider.
    • Ronny did more work updating documentation and links in a number of places.

Calendar of Events

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-12309: AlarmLifecycleListenerManagerIT and AlarmdIT flapping
  • NMS-12368: Create a step-by-step guide how to setup Kafka for Minions
  • NMS-12375: Migrate guide to run with Docker from GitHub repo to Installation guide
  • NMS-12385: Discovery does not honor exclude-range inside a definition
  • NMS-12386: Discovery exclude-range is not location-aware
  • NMS-12396: Enhance new snmp profiles to allow fitting to nodes inside requisitions without SNMP service associated to any IPs configured
  • NMS-12399: SNMP profile fitting is not triggered in some cases when MINION is involved
  • NMS-12408: Add possibility to listen for graph changes
  • NMS-12412: Alarmd fails intermittently and OOMs
  • NMS-12413: SNMP Remove from definitions fails for definitions with profile label

by RangerRick at December 02, 2019 07:23 PM

November 25, 2019

OpenNMS On the Horizon – November 25th, 2019 – Bug Fixes, BMP in Telemetryd, Time-Series APIs, Helm, and More!

It's time for OpenNMS On the Horizon!

In the last week we continued to work on fixing bugs and doing new work on BMP support in Telemetryd and time-series API improvements. Also, Helm got some fixes for Grafana 6.4 and a new release.

Github Project Updates

  • Internals, APIs, and Documentation

    • Ronny continued his work on expanding the documentation for setting up Kafka and Minions.
    • Dustin did more work on adding support for BMP to Telemetryd.
    • Chandra worked on wrapping up exclude-range fixes in SNMP definitions.
    • Jesse worked on fixing some issues in Drools and Alarmd.
    • Markus continued working on improvements to the graph API.
    • Dustin did more work on adding support for custom headers in PageSequenceMonitor and HttpPostMonitor.
    • Patrick worked on some proof-of-concept code for a new time-series API.
    • Chandra fixed SNMP profiles to be processed during provisioning node scan.
  • Web, ReST, and UI

    • I fixed an issue with the Flows datasource in Helm, as well as some other cosmetic fixes.
    • Markus did a little more work on his universal search changes.

Helm 4.0.2 Released

Last week, Helm -- the OpenNMS plugin for Grafana -- got updated to 4.0.2. RPM and Debian packages have been released, and we are waiting for Grafana to update their plugin registry with the change as well.

This release fixes a bug with the Flow datasource and Grafana 6.4, as well as some other cosmetic changes to the Flow query interface.

Calendar of Events

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-192: Rendering Bug in Flow Query Builder
  • HELM-193: Conversation Flow Histogram show "null" instead of Unknown/Other in legend
  • NMS-12347: Provide Central Search Function
  • NMS-12379: "Page Not Found" in alarm-list when choosing number of alarms in dropdown-list
  • NMS-12387: Update OpenJDK 11.0.4 to 11.0.5
  • NMS-12389: Implement caching strategies for graphs
  • NMS-12393: Add HTTP header injection in HTTP Monitors

by RangerRick at November 25, 2019 04:21 PM

November 18, 2019

OpenNMS On the Horizon – November 18th, 2019 – Bug Fixes, CircleCI, BMP Support, Helm, and More!

It's time for OpenNMS On the Horizon!

In the last week we fixed more bugs and worked on other infrastructure, as well as continuing work on BMP support and a Grafana 6.4 Helm fix.

Github Project Updates

  • Internals, APIs, and Documentation

    • Markus continued to work on graph API improvements.
    • I added support for building (and signing) Debian packages in the CircleCI workflow.
    • Christian worked on adding support for defining custom headers in the HttpPostMonitor and PageSequenceMonitor.
    • Ronny worked on a bunch of updated Docker and other container documentation.
    • Patrick worked on normalizing all our Karaf shell commands.
    • Ronny and I fixed the hour-rendering bug in send-event.pl introduced in Horizon 25.1.0.
    • Christian did more work on adding BMP support to Telemetryd.
    • Christian fixed an issue with WS-Man polling on Minion.
    • Chandra did more work on fixing exclude-range support in the discovery config.
  • Web, ReST, and UI

    • I fixed an issue with the Flow data source in the Helm Grafana plugin.

Calendar of Events

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • HELM-190: TypeError: Cannot read property 'toBits' of undefined
  • NMS-12365: Cannot use poller:poll karaf command with WsManMonitor through Minions
  • NMS-12367: Upstream Drools Bug: From with modify fires unexpected rule
  • NMS-12369: FlowStackKafkaIT hanging on CircleCI
  • NMS-12388: Allow persisting edges with references to at least one vertex which is not in the edge's namespace
  • NMS-12392: send-event.pl is broken after OpenNMS 25.1.0 update
  • NMS-12398: Use OpenJDK 8 JDK for build environment

by RangerRick at November 18, 2019 06:50 PM

November 12, 2019

OpenNMS On the Horizon – November 12th, 2019 – Bug Fixes, Docker and CI, Releases, and More!

It’s time for OpenNMS On the Horizon!

In the last week we fixed some bugs, worked on Docker and CI, and did the monthly Horizon and Meridian releases.

Github Project Updates

  • Internals, APIs, and Documentation
    • Patrick fixed a bug where the config tester didn’t catch a missing datacollection file.
    • Markus continued his work on enhancing graph querying to handle semantic zoom level and focus, as well as enriching graphs with additional node data.
    • Ronny and I worked on docker container updates.
    • Christian fixed the WS-Man poller.
    • I updated our CircleCI config to sign RPMs.
    • Chandra fixed discovery to honor <exclude-range> inside a definition.
    • Jesse worked on updating to the latest Drools engine.
  • Web, ReST, and UI
    • Alejandro fixed some issues in the requisition UI.
    • I worked on a Helm issue that could prevent adding a new flow histogram panel.

November Releases: Meridian 2016 through 2019, Horizon 25.1.0

Last week, we released Horizon 25.1.0 with a number of enhancements targeting our long-term-support release of Meridian 2019.

For a complete list of changes, see the release notes:

Calendar of Events

  • December Releases - December 3rd, 2019

    The next OpenNMS release day is December 3rd.

    So far we expect to be putting out the following releases:

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-10396: Config tester doesn’t detect missing xml datacollection file
  • NMS-12120: Readiness probe with Minion in Kubernetes with health:check does not work
  • NMS-12339: Clarify that LDAPS is supported for external authentication
  • NMS-12376: Allow querying a graph using vertices in focus and a szl
  • NMS-12377: Listing monitoring locations from the administrative WebUI is not working
  • NMS-12380: Build failure during release for 25.1.0 in CircleCI
  • NMS-12382: Implement Enrichment of vertices
  • NMS-12384: backport missing patches from 25.1.0 to foundation-2019

by RangerRick at November 12, 2019 08:24 PM

November 06, 2019

OpenNMS 2019.1.0 (Mercury) Released

Release 2019.1.0 is the first release in the Meridian 2019 series.

The codename for 2019.1.0 is Mercury.

 

What’s New in Meridian 2019

Since Meridian 2018, we have introduced a large number of features, most notably Telemetryd (for processing streaming telemetry like NetFlow and sFlow), the Sentinel (for horizontal scaling of telemetry and other processing), and ALEC (for alarm correlation).

On top of that, there have been many other improvements and bug fixes since Meridian 2018.

Meridian 2019 roughly matches the feature set available in Horizon 25.

Architecture for Learning Enabled Correlation

Horizon 23 introduced support for correlation of alarms into meta-alarms called "situations" using an engine called the Architecture for Learning Enabled Correlation.

Situations are OpenNMS alarms that contain one or more triggering alarms, which allows them to be browsed, acknowledged, and unacknowledged just like any other alarm.

A high-level overview of the goal and implementation of correlation can be seen on the ALEC web site.

Changes to the Alarm Lifecycle
Alarm Clearing

Traditionally, OpenNMS has created and resolved alarms in pairs, with one alarm representing the triggering event (or events), and then a second alarm representing the resolution. Horizon 23 changes this default behavior to use a single alarm to track the problem state, incrementing the alarm count when it occurs while in a problem state, or when moving from resolved back into a problem state. Additionally, you can configure OpenNMS to create a new alarm if a problem happens again.

These behaviors are controlled by the introduction of 2 new settings in the opennms.properties file:

org.opennms.alarmd.legacyAlarmState
This setting reverts to the old (pre-23) behavior of creating separate alarms for a problem and its resolution.
org.opennms.alarmd.newIfClearedAlarmExists
This setting forces Alarmd to create a new alarm if a problem reoccurs, rather than incrementing an existing alarm. (Note: this is ignored if legacyAlarmState is set to true.)

These improvements are covered in a lunch and learn video we published recently, if you would like to learn more.

Alarmd Architecture

To facilitate the implementation of ALEC, alarmd has been rearchitected to use Drools to manage the alarm lifecycle, rather than Vacuumd automations, triggers, and actions.

If are migrating changes to vacuumd-configuration.xml from an earlier Meridian release, it is strongly recommended you port them to the new Alarmd Drools context. The Drools rules are in the $OPENNMS_HOME/etc/alarmd/drools-rules.d/ directory.

Additionally, we no longer generate alarmCreated, alarmEscalated, alarmCleared, alarmUncleared, alarmUpdatedWithReducedEvent, and alarmDeleted events. Instead, it is recommended that you add Drools rules to react to alarm changes.

For more complicated integrations, we also have a new API — AlarmLifecycleListener — for reacting to alarm changes.

Kafka Data Collection Sync

In addition to publishing events, alarms, and node inventory to Kafka, we now publish collected time-series data to the Kafka bus as well.

Sentinel

In addition to the Minion, we have added a new container-based subsystem called "Sentinel." The Sentinel is a Karaf container that can be configured to run a subset of OpenNMS daemons as a standalone tool, to aid in horizontal scaling and/or high availability.

Sentinel is designed to run our Karaf/Camel/SQS-based messaging bus, syslog listener, telemetry receiver, and Newts and Elasticsearch persistence.

Node and Interface Metadata

There is now support for associating arbitrary metadata with nodes and interfaces, including configuring arbitrary metadata in the requisition UI.

For details on using the metadata APIs, see the Admin Guide and the Developer Guide.

Elasticsearch 7.x Support

All of the features that leverage integrations with Elasticsearch i.e. event & alarm history, flows & situation feedback have been updated to support Elasticsearch 7.x. Elasticsearch versions before 7.x are no longer supported.

Given the pace of changes and the number of breaking changes between major versions of Elastisearch, we will focus on supporting a single major version of Elasticsearch per release moving forward.

Other Improvements

Since Meridian 2019 is based on Horizon 25, it contains all the fixes and updates that have occurred since Meridian 2018 was created from the Horizon 21 codebase.

For a more complete list of changes included in this release, see the "What’s New" documentation for the following Horizon releases:

by RangerRick at November 06, 2019 02:17 AM

OpenNMS Horizon 25.1.0 (Momo) Released

Release 25.1.0 is the second release in the Horizon 25 series.

It contains a bunch of bug fixes and enhancements, including packaging fixes, BSM updates, alarmd improvements, and much more.

The codename for 25.1.0 is Momo.

  Note: This release contains a couple of breaking changes:

  1. Dates in event XML (in the ReST API and published to the event port) now must be formatted in standard ISO-8601 format (eg, 2019-11-05T14:36:00-04:00).
  2. Scriptd has been changed to execute scripts in a single read-only transaction by default. If you need the ability to write changes to the database or need to do your own transaction management for any other reason, you will need to add transactional="false" to the <scriptd-configuration …​> tag in the scriptd-configuration.xml file.
Bug
  • removed service will break BSM web ui (Issue NMS-9322)
  • Event parameters no longer preserve ordering (Issue NMS-9827)
  • The JMX-Cassandra service goes down for all the cluster when a single instance is down. (Issue NMS-10027)
  • deleting a BSM monitor while an alarm is active doesn’t clear the alarm (Issue NMS-10184)
  • default event description is incorrect (Issue NMS-10346)
  • Config tester doesn’t detect missing xml datacollection file (Issue NMS-10396)
  • Minion fails to start on Raspberry Pi (Issue NMS-10447)
  • BSM alarm severity is not being updated (Issue NMS-10578)
  • snmp authentication error traps with Enhanced Linkd / bridge discovery (Issue NMS-10582)
  • Elasticsearch forwarding fails to recover after outage (Issue NMS-10697)
  • Flow rest results for top N queries are not returned in the correct order (Issue NMS-12104)
  • Flow Classification not functioning as expected (Issue NMS-12259)
  • ReST API for meta-data doesn’t support JSON (Issue NMS-12272)
  • UI for meta-data is only present when using the horizontal layout (Issue NMS-12273)
  • Groups disappear in classification UI (Issue NMS-12291)
  • BSM simulation mode does not reset the last state (Issue NMS-12302)
  • Docker image for sentinel runs the process as root (Issue NMS-12311)
  • Docker image for Minion runs with UID 1001 but the minion user has UID 997 (Issue NMS-12312)
  • Web Assets Dependency Rollup 2019-09-24 (Issue NMS-12320)
  • Memory leak in Drools engine for alarmd (Issue NMS-12322)
  • Minion RPM upgrade deletes /opt/minion (Issue NMS-12324)
  • Threshold state keys do not incorporate the collected resource’s instance label (Issue NMS-12329)
  • Reportd generated reports cause: "No bean named '' is defined" in Persisted Reports (Issue NMS-12337)
  • InterfaceNodeCache doesn’t remove deleted nodes immediately (Issue NMS-12338)
  • Delivering a report with "-" in local part of email address is not working (Issue NMS-12342)
  • XMLMarshalException in ipc.log: Unexpected close tag </inst>; expected </instance> (Issue NMS-12343)
  • Update installation guide to CentOS 8 (Issue NMS-12348)
  • Install guide for R-core is broken for CentOS 8 (Issue NMS-12352)
  • Karaf feature install issue with opennms-core-tracing-jaeger (Issue NMS-12359)
  • Fix requisition cache when accessing the Requisitions UI via "Edit in Requisition" (Issue NMS-12360)
  • Listing monitoring locations from the administrative WebUI is not working (Issue NMS-12377)
Enhancement
  • Add more information into BSM alarms (Issue NMS-9352)
  • Refactor the compatibility matrix in the documentation (Issue NMS-9684)
  • Be able to change the number of rows for the pagination control on the Requisitions UI (Issue NMS-9793)
  • Documentation typo for /rest/ifservices on the developers guide (Issue NMS-9842)
  • Add Web-Hook as delivery option (Issue NMS-12153)
  • Refactor Event Timestamps to ISO-8601 Format (Breaking Change) (Issue NMS-12263)
  • Improve robustness of CassandraBlobStore for async operations (Issue NMS-12274)
  • Clearing threshold states via shell should take effect immediately and not require restart (Issue NMS-12277)
  • List Kafka RPC/Sink topics, Expose Metrics on Karaf shell (Issue NMS-12294)
  • Create proper systemd files for OpenNMS, Minion and Sentinel (Issue NMS-12299)
  • Add ability to update definitions when SNMP profile changes (Issue NMS-12307)
  • Fix security vulnerability with jackson-databind (Issue NMS-12308)
  • Availability boxes on node pages including sub pages differ (Issue NMS-12321)
  • OpenNMS 25 Dependency Still Allows Old PostgreSQL Versions (Issue NMS-12341)
  • Update base container image to use CentOS 8 (Issue NMS-12353)
  • Remove floating OpenJDK dependencies in OCI build (Issue NMS-12354)
  • Detect and help resolve Karaf bootstrap issues (Issue NMS-12356)
  • Update CISCO-ENTITY-SENSOR-MIB threshold trap events to include alarm-data (Issue NMS-12362)
  • switch core/web-assets from yarn to npm (Issue NMS-12363)
  • Collect and display file descriptor statistics via JMX for OpenNMS and Minion (Issue NMS-12364)

by RangerRick at November 06, 2019 01:24 AM

November 05, 2019

OpenNMS Meridian 2018.1.13 (Flood) Released

Release 2018.1.13 is a small update to 2018.1.12 that fixes a few UI bugs.

The codename for 2018.1.13 is Flood.

Bug
  • Listing monitoring locations from the administrative WebUI is not working (Issue NMS-12377)
Enhancement
  • Availability boxes on node pages including sub pages differ (Issue NMS-12321)

by RangerRick at November 05, 2019 09:31 PM

OpenNMS Meridian 2017.1.20 (Lisbon) Released

Release 2017.1.20 is a small update to 2017.1.19 that fixes an issue with the display of availability on the node page.

The codename for 2017.1.20 is Lisbon.

Enhancement
  • Availability boxes on node pages including sub pages differ (Issue NMS-12321)
  • Clarify that LDAPS is supported for external authentication (Issue NMS-12339)

by RangerRick at November 05, 2019 07:09 PM

OpenNMS Meridian 2016.1.23 (Balthasart) Released

Release 2016.1.23 is a small update to 2016.1.22 that fixes an issue with the display of availability on the node page.

The codename for 2016.1.23 is Balthasart.

Story
  • Add a command to show configuration diffs (Issue NMS-12129)
  • Availability boxes on node pages including sub pages differ (Issue NMS-12321)

by RangerRick at November 05, 2019 06:37 PM

November 04, 2019

OpenNMS On the Horizon – November 4th, 2019 – Bug Fixes, Debugging Tools, Documentation Updates, Helm, and More!

It’s time for OpenNMS On the Horizon!

In the last 2 weeks we fixed a bunch of bugs, improved tools for debugging running systems, updated docs, fixed Helm, and more!

Github Project Updates

  • Internals, APIs, and Documentation
    • Ronny worked on updates to our Docker images to use CentOS 8.
    • Markus did more work on supporting sending reports to a webhook.
    • I fixed the new unified Minion packages to properly upgrade from Horizon < 25.
    • Chandra continued to work on updating discovery to support detectors.
    • Chandra fixed a bug in the node-interface cache that could cause issues when nodes are deleted.
    • Chandra fixed an issue with duplicate chunks in large Karaf messages.
    • Chandra added support for listing Kafka RPC/sink topics and metrics in the Karaf shell.
    • Jeff updated the threshold trap events for CISCO-ENTITY-SENSOR-MIB to include alarm data.
    • I fixed the OpenNMS packages to depend on the correct PostgreSQL version(s).
    • Jesse fixed a bug in Drools alarm processing that could cause a memory leak.
    • Chandra changed Provisiond so it can run script policies at the end of the node scan.
    • Alejandro made JMX configuration updates for collecting file descriptor statistics.
    • Ronny updated the compatibility matrix in the docs, and moved it to the install guide.
    • Chandra updated the SNMP agent config handling to update definitions when profiles change.
    • Jesse and Patrick worked on a daemon to watch for common startup issues, log them, and shut down gracefully.
    • Will Keaney worked on an update to the embedded Drools to version 7.18.0 to fix rule-processing bugs.
    • Patrick finished up his work on fixing event parameter ordering.
    • Ronny updated the docs to describe setting up Kafka for Minions.
    • Markus updated the new graph API to support a default focus.
  • Web, ReST, and UI
    • Christian did more work on making BSM handle deleted alarms gracefully.
    • Alejandro fixed an issue with cache handling in the requisition UI.
    • I fixed the way metadata is passed in the Helm entities datasource so it works in Grafana 6.4.
    • Alejandro added support for changing the number of pagination rows in the requisition UI.

Helm 4.0.1

Helm, the OpenNMS plugin suite for Grafana, has had a small update to 4.0.1.
This release only bumps some dependencies, and fixes running under Grafana 6.4.

It is available in the OpenNMS yum and apt repositories, and will be available
for installation through the Grafana CLI
once our pull request is merged.

Calendar of Events

  • November Releases - November 5th, 2019

    The next OpenNMS release day is November 5th.

    We expect to be putting out the following releases:

    • Horizon 25.1.0
    • Meridian 2016.1.23
    • Meridian 2017.1.20
    • Meridian 2018.1.13
    • Meridian 2019.1.0

    With the release of Meridian 2019.1.0, Meridian 2016 will be end-of-lifed.
    Security patches will continue to be applied for Powered By OpenNMS customers, but no new releases will be made.

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • ALEC-80: The Kafka Topic edgesTopic from the configuration is ignored
  • ALEC-81: OpenNMS Kafka - Format dates in ISO-8601
  • HELM-184: Fix Helm for Grafana 6.4
  • IPL-34: Update RHEL/CentOS IPLIKE Packages To Be Co-Installable
  • JS-45: Panel data error: TypeError: Cannot read property ‘id’ of undefined
  • NMS-9352: Add more information into BSM alarms
  • NMS-9684: Refactor the compatibility matrix in the documentation
  • NMS-9793: Be able to change the number of rows for the pagination control on the Requisitions UI
  • NMS-9827: Event parameters no longer preserve ordering
  • NMS-10346: default event description is incorrect
  • NMS-10396: Config tester doesn’t detect missing xml datacollection file
  • NMS-11979: Provide DefaultFocus capabilities
  • NMS-12153: Add Web-Hook as delivery option
  • NMS-12197: Flapping KafkaOffsetIT
  • NMS-12288: BSM configuration breaks without being notifed
  • NMS-12294: List Kafka RPC/Sink topics, Expose Metrics on Karaf shell
  • NMS-12307: Add ability to update definitions when SNMP profile changes
  • NMS-12308: Fix security vulnerability with jackson-databind
  • NMS-12315: Update discoveryd to support detectors
  • NMS-12316: Provide criteria for determining the “management IP” in provisiond
  • NMS-12318: Process newSuspect events in a single threaded fashion
  • NMS-12322: Memory leak in Drools engine for alarmd
  • NMS-12324: Minion RPM upgrade deletes /opt/minion
  • NMS-12338: InterfaceNodeCache doesn’t remove deleted nodes immediately
  • NMS-12341: OpenNMS 25 Dependency Still Allows Old PostgreSQL Versions
  • NMS-12343: XMLMarshalException in ipc.log: Unexpected close tag ; expected
  • NMS-12352: Install guide for R-core is broken for CentOS 8
  • NMS-12353: Update base container image to use CentOS 8
  • NMS-12354: Remove floating OpenJDK dependencies in OCI build
  • NMS-12356: Detect and help resolve Karaf bootstrap issues
  • NMS-12359: Karaf feature install issue with opennms-core-tracing-jaeger
  • NMS-12360: Fix requisition cache when accessing the Requisitions UI via “Edit in Requisition”
  • NMS-12362: Update CISCO-ENTITY-SENSOR-MIB threshold trap events to include alarm-data
  • NMS-12363: switch core/web-assets from yarn to npm
  • NMS-12364: Collect and display file descriptor statistics via JMX for OpenNMS and Minion

by RangerRick at November 04, 2019 07:29 PM

October 25, 2019

OpenNMS.js v2.0.1

This is a small release with some dependency updates and a fix for handling of ReST data that is missing a response.

  • dao: handle .fromData when data is undefined (JS-45) (efe6858)
  • dao: warn if lastEvent is missing on an alarm (JS-45) (e4af27d)

by RangerRick at October 25, 2019 07:51 PM

October 21, 2019

OpenNMS On the Horizon – October 21st, 2019 – Bug Fixing, Packaging, Detectors and Discovery, Reporting, Helm, and More!

It’s time for OpenNMS On the Horizon!

In the last week we worked on lots of small bug fixes, packaging updates and improvements, adding detectors to discovery, reporting, and Helm.

Github Project Updates

  • Internals, APIs, and Documentation
    • Markus worked on fixing report delivery to some email addresses.
    • Patrick continued to work on fixing event parameter ordering.
    • I wrapped up my work fixing up the OpenNMS systemd service file as well as adding Minion and Sentinel native systemd services.
    • Ronny fixed up a bunch of compatibility and installation issues in the documentation.
    • I fixed an issue with upgrades when moving to the new monolithic Minion RPMs.
    • Chandra fixed an issue where kafka sync API chunks could be processed twice if a retry has occurred.
    • Christian fixed an issue with alarm clearing and BSM.
    • Chandra continued his work on being able to run detectors as part of the discovery process.
    • Alejandro fixed a configuration issue where the JMX-Cassandra service could be shown as “down” even if only one instance in the cluster is down.
    • Alejandro fixed a bug in the event description for interfaceAdminUp.
    • Patrick worked on cleaning up the rest of our Karaf shell commands to start with opennms for consistency.
    • Ronny worked on a bunch of doc updates to default to CentOS 8 for RPM installs.
  • Web, ReST, and UI
    • Markus worked on fixing Reportd-generated reports not being downloadable in the new UI.
    • Markus worked on adding support for sending a generated report to a URL as a webhook.
    • Markus continued work on his proof-of-concept universal search bar.
    • I worked on fixing Helm to work with Grafana 6.4.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-9842: Documentation typo for /rest/ifservices on the developers guide
  • NMS-10027: The JMX-Cassandra service goes down for all the cluster when a single instance is down.
  • NMS-10184: deleting a BSM monitor while an alarm is active doesn’t clear the alarm
  • NMS-10582: snmp authentication error traps with Enhanced Linkd / bridge discovery
  • NMS-12263: Refactor Event Timestamps to ISO-8601 Format (Breaking Change)
  • NMS-12299: Create proper systemd files for OpenNMS, Minion and Sentinel
  • NMS-12302: BSM simulation mode does not reset the last state
  • NMS-12337: Reportd generated reports cause: “No bean named ‘’ is defined” in Persisted Reports
  • NMS-12342: Delivering a report with “-” in local part of email address is not working
  • NMS-12348: Update installation guide to CentOS 8

by RangerRick at October 21, 2019 07:10 PM

October 14, 2019

OpenNMS On the Horizon – October 14th, 2019 – Minion, Sentinel, Date Parsing, SNMP Profiles, Discovery, Search, and More!

It’s time for OpenNMS On the Horizon!

In the last week we worked on a number of bugs mostly related to Minion and Sentinel, plus date parsing, SNMP profiles, discovery, universal search, and more!

Github Project Updates

  • Internals, APIs, and Documentation
    • Marcel and Markus worked on cleaning up the JMX configuration for monitoring JVMs.
    • Patrick continued to work on making sure event parameter order is preserved.
    • Chandra worked on fixing an issue where the Minion could stop sending data over Kafka.
    • Matt continued his work on improving async operations against Cassandra.
    • Chandra worked on adding detector support to discovery.
    • I worked on fixing some packaging issues with Minion and Sentinel, as well as improving systemd startup and shutdown.
    • Christian worked on a number of bugs in BSM’s backend.
    • Matt fixed an issue with clearing threshold states on the Karaf shell.
    • I updated startup to always use the (new) CLDR locale data, which includes a breaking change to event serialization to always use ISO-8601 dates.
    • Chandra did more work on his code to update SNMP definitions when the profile is updated.
    • Chandra worked on fixing some issues in the node/IP cache.
    • Matt fixed an issue with invalid key caching in thresholding state.
  • Web, ReST, and UI
    • Markus revived his work during Dev-Jam on a “universal” search for the OpenNMS web UI.

Release Day Moving

Moving to monthly releases has been a huge success.
It’s made it easier to anticipate upgrades, to tell users when a bug fix will make a release, and it’s (generally *cough*) taken the pressure off to get some specific feature into a release.

However, we originally picked Thursday as a release day because our weekly sprint meeting is Wednesday.
The idea was that we could go over what issues were wrapped up and make sure PRs got merged before the release Thursday.

In reality, Thursday only gave us just enough time to realize which important things wouldn’t make it in and not really have anything to do about it.

The new release day is (drumroll):

The First Tuesday of the Month

This means that we can encourage important PRs to get merged by Friday, which gives CI a chance to run over the weekend, including our weekly run of “Dependency Monkey” which goes through every Maven dependency in the OpenNMS source tree and builds it individually to be sure we don’t have any transient dependencies that can cause build problems.

That gives us Monday to fix any critical issues and get them merged before a Tuesday release.

The first Tuesday release will be November 5th, 2019.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-9322: removed service will break BSM web ui
  • NMS-10578: BSM alarm severity is not being updated
  • NMS-10697: Elasticsearch forwarding fails to recover after outage
  • NMS-12274: Improve robustness of CassandraBlobStore for async operations
  • NMS-12277: Clearing threshold states via shell should take effect immediately and not require restart
  • NMS-12307: Add ability to update definitions when SNMP profile changes
  • NMS-12317: instance/group ID is not being honored in some minion/sentinel code
  • NMS-12329: Threshold state keys do not incorporate the collected resource’s instance label

by RangerRick at October 14, 2019 01:36 PM

October 07, 2019

OpenNMS On the Horizon – October 7th, 2019 – Minion & Sentinel, Events and Alarms, Business Service Monitor, Flows, UI Improvements, and More!

It’s time for OpenNMS On the Horizon!

In the last week we worked on the Minion and Sentinel runtimes, event and alarm bugs, BSM, flow updates, UI improvements, and more!

Github Project Updates

  • Internals, APIs, and Documentation
    • Ronny worked on some fixes for running Minion and Sentinel as non-root.
    • Patrick did more work on making sure event parms are sorted correctly.
    • Chandra worked on fixing some issues with exception-handling when sending flows into Kafka.
    • Markus did more work on fixing Elasticsearch forwarding recovery when an outage occurs.
    • I worked on cleaning up some places in the code where the default instance ID wasn’t set up properly, in preparation for Meridian 2019.
    • Christian fixed a few issues with BSM, including alarm severities not updating properly and issues when services are deleted.
    • Markus did some work to wrap up Jeff’s fixes to the Slack notification strategy.
    • Jesse did some work on remote poller modernization.
    • I worked on changing event/alarm time serialization to use ISO-8601 rather than local-based timestamps. (including an update to send-event.pl)
    • I did more work on native systemd configs for Minion and Sentinel.
    • Matt made some improvements to async operations on the CassandraBlobStore.
    • I worked on fixing an upgrade issue with the minion packaging.
    • Marcel Fuhrmann created some configurations to enrich our node asset information using the SNMP Asset Adapter for the following products:
  • Web, ReST, and UI
    • Markus fixed an issue with groups disappearing in the classification UI.
    • I released OpenNMS.js 2.0.
    • Markus did more work on his refresh/improvements to the navbar.
    • Markus fixed an issue where severities were styled differently between the node page and sub-pages.
    • Markus fixed a problem where the meta-data editor wouldn’t show in virtical layout mode.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last OOH

  • NMS-10564: Shorten log message in SNMP trap event definitions
  • NMS-12104: Flow rest results for top N queries are not returned in the correct order
  • NMS-12128: Rework the current navbar
  • NMS-12259: Flow Classification not functioning as expected
  • NMS-12273: UI for meta-data is only present when using the horizontal layout
  • NMS-12311: Docker image for sentinel runs the process as root
  • NMS-12312: Docker image for Minion runs with UID 1001 but the minion user has UID 997
  • NMS-12320: Web Assets Dependency Rollup 2019-09-24
  • NMS-12321: Availability boxes on node pages including sub pages differ
  • PRIS-151: Allow node-level meta-data

by RangerRick at October 07, 2019 03:42 PM

September 30, 2019

OpenNMS.js v2.0.0

OpenNMS.js 2.0 adds a few new APIs, contains a ton of refactoring and build system updates, and has a number of breaking changes.

Notable Changes:

  • updated CLI libraries to fix/improve table output
  • better, faster build system to improve generated code
  • improved handling of authentication in HTTP implementations
  • support for HEAD requests has been added to the HTTP implementations
  • a number of metadata objects (notably OnmsServer) support .equals() for comparison now
  • property caching on v2 API calls is fixed when interacting with multiple servers/DAOs
  • filter API now supports orderBy and order (and the alarms CLI list command supports it)
  • HTTP parameters in OnmsHTTPOptions can now have multiple values -- for example a parameter with value [ 1, 2 ] will serialize to &foo=1&foo=2

Breaking Changes:

  • The api/Log module now only exports a single, simplified log object; typescript-logging was overly complicated and not really adding much in the way of value. Use .setDebug(), .setQuiet(), and .setSilent() to change the logging level instead.
  • A number of the TypeScript APIs have been clarified to be explicitly nullable (and/or undefined-able) to make strict null- and type-checking validation pass.
  • PropertiesCache and its associated interface, ISearchPropertyAccessor are gone. This only affects you if you have implemented custom DAOs, which is very unlikely. :)
  • The previously deprecated timeout property in AbstractHTTP (and sub-classes) has been removed. Access the AbstractHTTP.options.timeout property directly.
  • The Client no longer keeps a separate copy of the server object. Instead you should access the http.server sub-property directly.
  • A number of API objects are now immutable/read-only to reduce side-effects: OnmsAuthConfig, OnmsEnum, OnmsError, OnmsHTTPOptions, OnmsResult, OnmsServer, Operator, SearchPropertyType, ServerMetadata, TicketerConfig.
    The OnmsHTTPOptions and OnmsServer objects now have builders (use .newBuilder() to create) rather than constructors with a bunch of arguments.
  • The id property on OnmsServer is no longer generated, it is computed based on the contents of the server object and should be repeatably equal if the contents are equal.

by RangerRick at September 30, 2019 08:33 PM

A Low Bandwidth Camera Solution

My neighbor recently asked me for advice on security cameras. Lately when anyone asks me for tech recommendations, I just send them to The Wirecutter. However, in this case their suggestions won’t work because every option they recommend requires decent Internet access.

I live on a 21 acre farm 10 miles from the nearest gas station. I love where I live but it does suffer from a lack of Internet access options. Basically, there is satellite, which is slow, expensive and with high latency, or Centurylink DSL. I have the latter and get to bask in 10 Mbps down and about 750 Kbps up.

Envy me.

Unfortunately, with limited upstream all of The Wirecutter’s options are out. I found a bandwidth calculator that estimates a 1 megapixel camera encoding video using H.264 at 24 fps in low quality would still require nearly 2 Mbps and over 5 Mbps for high quality. Just not gonna happen with a 750 Kbps circuit. In addition, I have issues sending video to some third party server. Sure, it is easy but I’m not comfortable with it.

I get around this by using an application called Surveillance Station that is included on my Synology DS415+. Surveillance Station supports a huge number of camera manufacturers and all of the information is stored locally, so no need to send information to “the cloud”. There is also an available mobile application called DS-cam that can allow you to access your live cameras and recordings remotely. Due the the aforementioned bandwidth limitations, it isn’t a great experience on DSL but it can be useful. I use it, for example, to see if a package I’m expecting has been delivered.

DS-Cam Camera App

[DS-Cam showing the current view of my driveway. Note the recording underneath the main window where you can see the red truck of the HVAC repair people leaving]

Surveillance Station is not free software, and you only get two cameras included with the application. If you want more there is a pretty hefty license fee. Still, it was useful enough to me that I paid it in order to have two more cameras on my system (for a total of four).

I have the cameras set to record on motion, and it will store up to 10GB of video, per camera, on the Synology. For cameras that stay inside I’m partial to D-Link devices, but for outdoor cameras I use Wansview mainly due to price. Since these types of devices have been known to be easily hackable, they are only accessible on my LAN (the “LAN of things”) and as an added measure I set up firewall rules to block them from accessing the Internet unless I expressly allow it (mainly for software updates).

To access Surveillance Station remotely, you can map the port on the Synology to an external port on your router and the communication can be encrypted using SSL. No matter how many cameras you have you only need to open the one port.

The main thing that prevented me from recommending my solution to my neighbor is that the DS415+ loaded with four drives was not inexpensive. But then it dawned on me that Synology has a number of smaller products that still support Surveillance View. He could get one of those plus a camera like the Wansview for a little more than one of the cameras recommended by The Wirecutter.

The bargain basement choice would be the Synology DS118. It cost less than $200 and would still require a hard drive. I use WD RED drives which run around $50 for 1TB and $100 for 4TB. Throw in a $50 camera and you are looking at about $300 for a one camera solution.

However, if you are going to get a Synology I would strongly recommend at least a 2-bay device, like the DS218. It’s about $70 more than the DS118 and you also would need to get another hard drive, but now you will have a Network Attached Storage (NAS) solution in addition to security cameras. I’ve been extremely happy with my DS415+ and I use it to centralize all of my music, video and other data across all my devices. With two drives you can suffer the loss of one of them and still protect your data.

I won’t go in to all of the features the Synology offers, but I’m happy with my purchase and only use just a few of them.

It’s a shame that there isn’t an easy camera option that doesn’t involve sending your data off to a third party. Not only does that solution not work for a large number of people, you can never be certain what the camera vendor is going to do with your video. This solution, while not cheap, does add the usefulness of a NAS with the value of security cameras, and is worth considering if you need such things.

by Tarus at September 30, 2019 06:00 PM

OpenNMS On the Horizon – September 30th, 2019 – UI Updates, Flow Changes, and More!

It’s time for OpenNMS On the Horizon!

In the last week we did more cleanup in prep for Horizon 25, including UI fixes, flow changes, and more!

Github Project Updates

  • Internals, APIs, and Documentation
    • I continued to work on cleaning up systemd startup for Minion and Sentinel.
    • Chandra worked on making it possible to list RPC/sink topics from the Karaf shell.
    • Jesse fixed a potential ConcurrentModificationException in the event translator.
    • Patrick continued to work on making sure event parameters are always ordered correctly.
    • Markus worked on a set of flow classification Karaf shell commands, as well as a number of other flow classification bugs.
    • Dustin fixed an issue processing sFlow packets without IP information.
    • Chandra worked on making SNMP definitions update when the profile has changed.
    • Christian started working on adding Meta-Data support to PRIS.
    • Ronny did a bunch of updates to docker image publishing.
    • I did more work on updating events to use ISO-8601 dates when serializing (and parsing).
  • Web, ReST, and UI
    • Markus did more work exposing health:check info through ReST.
    • Jesse finished cleaning up the Jasper Studio integration.
    • Chandra moved the “Telephone PIN” in the notification UI with related relevant bits.
    • Jesse fixed an issue with timeouts in the new Grafana report client.
    • Christian fixed the Meta-Data ReST API to support JSON output.
    • Ronny updated Jetty to version 9.4.20.v20190813.

OpenNMS September Releases

In September we had Meridian 2017 and 2018 releases, as well as a new major Horizon release: Horizon 25.

OpenNMS Horizon 25

Horizon 25 contains a huge number of bug fixes and enhancements, most notably massive thresholding improvements, big changes to netflow and other streaming telemetry data, reporting and UI updates, plus much more.

For an overview of what has changed since Horizon 24, see What’s New in OpenNMS Horizon 25. For a complete list of changes, see the Horizon 25.0.0 release notes.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

– Ben

Resolved Issues Since Last OOH

  • HELM-182: Update icons entity and flow datasources
  • HELM-183: Custom panels fail to render as PNGs
  • NMS-10073: Telephone PIN Field in User Details is Misplaced
  • NMS-12190: Enable flow UDP listener by default on Minion and OpenNMS
  • NMS-12230: Verify Database Reporting Documentation is still up to date
  • NMS-12246: Documenting Thresholding for H25
  • NMS-12272: ReST API for meta-data doesn’t support JSON
  • NMS-12285: Poller take a long time to startup/initialize on large systems
  • NMS-12291: Groups disappear in classification UI
  • NMS-12297: Grafana report generation is timing out
  • NMS-12298: Expose health:check via ReST
  • NMS-12300: Update Minion packaging to use single RPM/Deb
  • NMS-12306: ConcurrentModificationException when cloning events
  • OIA-21: Tag and release OIA v0.2.1
  • PRIS-151: Allow node-level meta-data

by RangerRick at September 30, 2019 04:04 PM

September 26, 2019

OpenNMS Horizon 25.0.0 Released

Release 25.0.0 is the first release in the Horizon 25 series.

It contains a huge number of bug fixes and enhancements, most notably massive thresholding improvements, big changes to netflow and other streaming telemetry data, reporting and UI updates, plus much more.

The codename for 25.0.0 is Baozi.

For an overview of what has changed since Horizon 24, see What’s New in OpenNMS Horizon 25.  For a complete list of changes, see the Horizon 25.0.0 release notes.

by RangerRick at September 26, 2019 08:51 PM

OpenNMS Meridian 2018.1.12 Released

Release 2018.1.12 is a small update to 2018.1.11 that fixes a number of (mostly UI) bugs.

The codename for 2018.1.12 is Hurricane Force.

Bug
  • “Graph all” fails with ‘Request Header Fields Too Large’ error (Issue NMS-8712)
  • No class found exception in OSGi for org.osgi.service.jdbc.DataSourceFactory (Issue NMS-9341)
  • Updating external lists referenced by include-url requires restart OpenNMS (Issue NMS-10071)
  • Telephone PIN Field in User Details is Misplaced (Issue NMS-10073)
  • Cannot change the type of a scheduled outage (Issue NMS-12255)
  • Short outages are not visible in Availability-Bar (Issue NMS-12262)
  • vmwarereqtool freezes and never return to the prompt after is executed (Issue NMS-12265)
  • On the scheduled outage UI, the day is displayed as null for weekly schedule (Issue LTS-233)
  • Using special characters on the scheduled outages name breaks the UI (Issue LTS-234)

by RangerRick at September 26, 2019 05:14 PM

OpenNMS Meridian 2017.1.19 Released

Release 2017.1.19 is a small update to 2017.1.18 that fixes an exception and adds a utility for viewing config changes.

The codename for 2017.1.19 is Ujjain.

Bug
  • No class found exception in OSGi for org.osgi.service.jdbc.DataSourceFactory (Issue NMS-9341)
Enhancement
  • Add a command to show configuration diffs (Issue NMS-12129)

by RangerRick at September 26, 2019 04:12 PM

September 23, 2019

OpenNMS On the Horizon – September 23rd, 2019 – Bug Fixes, Drools, Kafka, Flows, Helm, and More!

It’s time for OpenNMS On the Horizon!

In the last week or so we worked on fixing a bunch of small bugs in Drools, Kafka, flow handling, and more, as well as reporting and Helm updates.

Github Project Updates

  • Internals, APIs, and Documentation
    • Jesse updated our embedded Drools engine to 7.26.0, and improved the session-handling in the DroolsAlarmContext to not require locking, which speeds up processing considerably.
    • Jesse fixed an issue with Kafka alarm synchronization.
    • Markus fixed an issue where health:check would respond that Elasticsearch in opennms-flows was failing when it was not configured.
    • Jesse enabled the flow UDP listener by default on Minion and OpenNMS.
    • Markus updated the flow enrichment code to use our session transaction management utility.
    • Chandra fixed the script provisioning policy and Scriptd to greedily initialize the model objects passed into scripts.
    • Jesse made some updates to Kafka statistics collection.
    • Dustin continued his work on making the Meta-Data DSL work with PSM.
    • Marcel worked on cleaning up some JMX collection names.
    • Dustin fixed flow processing to ignore SFlow data without IP data.
    • I fixed the issue where Minion and Sentinel logs can appear in the root of the filesystem.
    • Markus fixed a bug in flow priority management.
    • Ronny updated the default container images to use RRDtool rather than JRobin.
    • I continued to work on figuring out the best way to handle new DateTime locale processing in JDK11.
    • Jesse updated threshold processing to handle pushed metrics from OIA.
    • Dustin worked on improving Poller startup time.
    • I changed the Minion packages to be a single package like Sentinel.
    • Markus worked on fixing some issues with Elasticsearch forwarding after an outage.
    • David Schlenk added STARTTLS support to the SSLCertExpireMonitor.
    • Patrick made custom SNMP auth handling for Cisco routers configurable.
    • Patrick worked on making sure event parameter ordering is preserved.
  • Web, ReST, and UI
    • Patrick fixed an issue with rendering reports.
    • I added support for ordering entity queries in Helm.
    • I updated Helm to use Grafana’s built-in FontAwesome fonts rather than embedding Ionicons.
    • I fixed the regression where Backshift graphs would not properly restrict zooming.
    • Markus worked on a ReST service for retrieving health check data.
    • Jesse updated the Helm icons for the Flow and Entity datasources.

OpenNMS Releases This Week

Because we were so close to having all blockers closed for Horizon 25, we decided to hold off a week so we could get it out the door rather than just doing another 24 bump. The September releases will be happening this Thursday.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

– Ben

Resolved Issues Since Last OOH

  • HELM-130: Dynamic Filtering
  • HELM-172: Update Default Alarm Table Columns
  • HELM-174: Enhance query to support an order by clause
  • HELM-181: Severity icons are no longer displayed
  • JS-44: Fix parameter serialization in GrafanaHTTP
  • NMS-8294: Expose the complete OnmsNode object in Scriptd to avoid LazyInitializationExceptions
  • NMS-10498: HealthCheck should not fail for ElasticSearch if flows are not enabled
  • NMS-10605: Syslog incorrect dates being parsed into database
  • NMS-10635: Zooming with Backshift is broken
  • NMS-10662: Update default notification configuration to leverage alarm autoacknowledgements
  • NMS-10672: Redesign default threshold events
  • NMS-10704: Insecure cache-control for session cookies
  • NMS-10724: Kafka alarm producer synchronization fails due to missing event
  • NMS-11719: Refactoring Docker Container Images towards Horizon 25
  • NMS-11857: Improve visibility of IPCs (Monitor Sink/RPC)
  • NMS-12125: karaf.log appears on the root file system when running Minion/Sentinel on Ubuntu/Debian.
  • NMS-12185: sFlow adapter drops flows due to NPE
  • NMS-12229: Ensure the reporting jar for jasperstudio is still working and containing all the relevant jars
  • NMS-12244: Remove session lock from Drools in alarmd
  • NMS-12247: Add support for meta-data fields in thresholding expressions
  • NMS-12252: Add support for STARTTLS to TLS certificate monitor
  • NMS-12258: DefaultReportWrapperService: failed to run or render report
  • NMS-12268: ScriptPolicy scripts encounter LazyInitializationException on calling node.getSnmpInterface()
  • NMS-12271: allow using fetched RPMs in build_container_image.sh
  • NMS-12283: Be able to execute ICMP requests through Java when running as non-root
  • NMS-12286: Ordering of classification groups does not work
  • NMS-12287: Wrong decoding of hex string
  • NMS-12290: Default settings in container image don’t write RRD files
  • NMS-12293: The Debian APT repositories for branches looks incomplete
  • NMS-12301: Default “90% Interface Throughput” Threshold Doesn’t Work
  • OIA-14: Extend Threshold configuration

by RangerRick at September 23, 2019 09:04 PM

September 16, 2019

OpenNMS On the Horizon – September 16th, 2019 – Poller and Thresholding, UI Fixes, Provisioning, Startup, and More!

It’s time for OpenNMS On the Horizon!

In the last week or so we worked on poller and thresholding updates, more UI fixes, provisioning, startup fixes and enhancements, and more!

Github Project Updates

  • Internals, APIs, and Documentation
    • Chandra backported support for refreshing include-url when a reload event is sent to Pollerd.
    • Patrick did more work on the classification rules reordering backend.
    • Jeff added collection and graph support for Netscaler vServer.
    • Matt worked on performance improvements to thresholding.
    • Jesse did more work on making it so unit and integration tests run a subset based on changes, rather than the full suite.
    • Chandra fixed an initialization issue in ScriptPolicy when interacting with the node object.
    • Christian fixed a deadlock issue in vmwarereqtool
    • I increased the default heap size in Horizon 25 to 2GB.
    • Chandra fixed a bug in inconsistent ipHostName handling when (re-)provisioning a host.
    • Ronny updated the default notifd configuration to use default auto-acknowledgment.
    • Chandra worked on fixing WS-Man under JDK11.
    • Matt added a Karaf command-line tool for managing thresholding persistent state.
    • Jesse fixed an issue with wiring and Newts.
    • Ronny fixed an issue with an incorrect PID file when spawning OpenNMS.
    • Jesse worked on migrating the resourcecli tool to Karaf shell commands.
    • Ronny added a healthcheck script to the Minion and Sentinel containers.
    • Ronny fixed some issues with running as non-root in the OpenNMS containers.
  • Web, ReST, and UI
    • I did more work on supporting “order by” in Helm (and OpenNMS.js) entity queries.
    • Christian fixed an issue in the scheduled outage editor when using special characters in outage names.
    • Patrick fixed a bug in cache-control and session cookie headers.
    • Christian fixed a bug in deleting in the scheduled outage ReST API.
    • Matt fixed an issue in the scan reports ReST API.
    • I fixed a problem in OpenNMS.js with processing parameters with multiple values.

FYI: Mattermost Chat Security Update

If you are using the Mattermost desktop client to connect to chat.opennms.com, make sure you have updated to the latest version. They have released a security update for a remote code execution exploit.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

– Ben

Resolved Issues Since Last OOH

  • HELM-180: Flow Histogram – Not showing Legend
  • JS-43: Update Outdated Dependencies
  • NMS-10071: Updating external lists referenced by include-url requires restart OpenNMS
  • NMS-10278: Neutralise the docs stylesheet
  • NMS-11721: Replace custom bash templating with Confd and streamline entrypoint script
  • NMS-11830: CircleCI
  • NMS-11834: Thresholding for streaming metrics & more
  • NMS-11836: Project Drift Enhancements
  • NMS-11844: Grafana Integration
  • NMS-11861: Enterprise Reporting Enhancements
  • NMS-11975: Grouped flow classification rules
  • NMS-11998: Top N hosts (flows)
  • NMS-12084: Trapd & Syslogd Kafka Support
  • NMS-12212: Show configured rule groups
  • NMS-12213: Edit (CRUD) rule groups via rest & gui
  • NMS-12216: JMX Metrics for Newts disappeared
  • NMS-12226: Wrong PID in opennms.pid
  • NMS-12233: Dependency based testing
  • NMS-12235: WS-MAN doesn’t work with JDK 11
  • NMS-12238: Update minimum required version of PostgresSQL for H25
  • NMS-12243: Leverage telemetry sequencing for better thresholding performance
  • NMS-12248: Manage persisted threshold state via shell
  • NMS-12249: DNS resolved hostname should always be reflected in ‘iphostname’ field in ipinterface table
  • NMS-12255: Cannot change the type of a scheduled outage
  • NMS-12265: vmwarereqtool freezes and never return to the prompt after is executed
  • NMS-12267: EnhancedLinkd-Thread-x-of-x – Null Pointer Exception
  • NMS-12270: Remove old comment from data source configuration
  • NMS-12275: Fix usage description of vmwarereqtool
  • NMS-12276: Increase default heap size to 2GB
  • NMS-12278: Add documentation about classification rule & group sorting
  • NMS-12280: Migrate resourcecli to the Karaf shell
  • NMS-12281: Add Karaf shell command to view raw sample stored in Newts

by RangerRick at September 16, 2019 04:36 PM

September 09, 2019

OpenNMS On the Horizon – September 9th, 2019 – Flows, CI, Threshd, UI Fixes, and More!

It’s time for OpenNMS On the Horizon!

In the last week or so we worked on flows, speeding up tests, thresholding config sharing, a few web UI fixes, and more.

Github Project Updates

  • Internals, APIs, and Documentation
    • Matt updated the sFlow adapter to set the sequence number.
    • Jesse did more work on making it so CI tests only run the subset that have changed based on previous branches.
    • Dustin continued his work making the meta-data DSL work with the PageSequenceMonitor.
    • I worked on refactoring some common shell code to a separate project, and making it so Minion and Sentinel can launch differently depending on JVM.
    • Chandra fixed Pollerd to reload on a reloadDaemon event.
    • Matt continued his work on persisting and sharing Threshd configuration.
    • Marcel worked on splitting up the default JMX datacollection config into separate files.
  • Web, ReST, and UI
    • Chandra worked on wrapping up fixes to handle “Request Header Fields Too Large” errors.
    • Patrick worked on a caching/cookie issue with web sessions.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

– Ben

Resolved Issues Since Last OOH

  • NMS-9341: No class found exception in OSGi for org.osgi.service.jdbc.DataSourceFactory
  • NMS-12237: Ops wallboard hanging due to Vaadin session deadlock
  • NMS-12238: Update minimum required version of PostgresSQL for H25
  • NMS-12256: Resource Graphs : Graph Selection fails to render when many resources are selected
  • NMS-12264: Rewrite test in ScheduleOutageIT for new UI
  • NMS-12266: split shell utilities into a separate module

by RangerRick at September 09, 2019 04:10 PM