OpenNMS On the Horizon – Syslog, DNS, Docs, Flows, Config Management, IFTTT, Vue UIs, Discovery ReST, Helm
Tags: ooh, configapi, dns, documentation
Published: 2021-08-16 18:40:46

---
title: OpenNMS On the Horizon – Syslog, DNS, Docs, Flows, Config Management, IFTTT, Vue UIs, Discovery ReST, Helm
published: true
cover_image: https://pbs.twimg.com/media/E7PfstXWQAQS9o-?format=jpg&name=large
date: 2021-08-16 17:45:37 UTC
tags: OOH,configapi,dns,docs
canonical_url: https://www.opennms.com/en/blog/2021-08-16-opennms-on-the-horizon-syslog-dns-docs-flows-config-management-ifttt-vue-uis-discovery-rest-helm/?utm_source=rss&utm_medium=rss&utm_campaign=opennms-on-the-horizon-syslog-dns-docs-flows-config-management-ifttt-vue-uis-discovery-rest-helm
---

Since last time, we worked on syslog DNS hostname resolution, provisioning docs, flapping tests, flow classification performance, config management, the IFTTT plugin, flow processing, form validation, Vue geomaps and UI proofs-of-concept, discovery config ReST APIs, and Helm ipInterface improvements.

<!--
git log --since='2021-08-09 00:00:00' --until='2021-08-16 00:00:00' --author=bamboo@opennms.org --invert-grep --all --no-merges --color=always --format='%Cblue%ai %Cgreen%aN %Creset%s %Cblue(%H)%Cred%d' --author-date-order | sort | less -R
-->

## Github Project Updates

### **Internals, APIs, and Documentation**

- Chandra worked on a fix and performance improvement for issues resolving hostnames for syslog messages.
- Mark did more work on updated provisioning documentation.
- I worked on fixing a few flapping tests.
- Stefan implemented an improved decision tree for doing flow classification.
- Freddy continued his work on implementing the new configuration management API.
- Christian worked on fixing broken triggers in the IFTTT plugin.
- Christian fixed a bug in flow processing when both the option and data record contain `FIRST_SWITCHED` or `LAST_SWITCHED`.

### **Web, ReST, UI, and Helm**

- Jeff did some work on cleaning up inputs on a few forms.
- Jane worked on wrapping up her proof-of-concept Vue UI for geomaps.
- Jesse and Mike continued the work on a proof-of-concept new OpenNMS UI using Vue.
- Yang Li continued his work on expanding ReST APIs for the discovery and provisioning process.
- I worked on adding ipinterface querying to the Helm entity datasource.

### Contributors

<!--
git log --since='2021-08-09 00:00:00' --until='2021-08-16 00:00:00' --all --color=always --no-merges --pretty=format:'%aN' | sed -e 's,^ *,,' -e 's, *$,,' | sort -u | grep -viE '(dependabot|Atlassian Bamboo|CI.CD System)' | sed -e 's,^,\* ,'
-->

Thanks to the following contributors for committing changes since last OOH:

- Benjamin Reed
- Chandra Gorantla
- Christian Pape
- Dustin Frisch
- Freddy Chu
- Jane Hou
- Jeff Gehlbach
- Jesse White
- Mark Mahacek
- Mike Rose
- Patrick Schweizer
- Stefan Wachter
- Yang Li

## Help Shape the Future of OpenNMS

As you may or may not have noticed from the commit messages in previous OOHs, we're starting to look into (finally!) reworking our UI beyond just the reskinning and tweaking we've done in the past.

Part of this involves actually bringing in folks who can help us do that. ![😃](https://s.w.org/images/core/emoji/13.1.0/72x72/1f603.png)

Chris Geyer joined the team as a UX Designer earlier this year, and he asked me to include this in OOH to make sure everyone sees it:

> The OpenNMS community is central to what we do, and our product team wants to hear from you. Please fill out this quick survey so we can learn about you and your answers will help improve the experience of using OpenNMS going forward.
> 
> You can also sign up to volunteer to provide feedback on work in progress so that we can design new ideas that can help your network operations thrive.
> 
> Thanks in advance for your help!
> 
> [https://www.opennms.com/opennms-user-survey/](https://www.opennms.com/opennms-user-survey/)

I'm looking forward to starting to see some of this work come together, it's been a long time coming.

## Release Roadmap

### August Releases

In August, we released updates to all OpenNMS Meridian versions under active support, as well as an update to Horizon 28.  
This is the final Meridian 2018 release, as it has reached end-of-life.

### Horizon 28.0.2

Release 28.0.2 contains a bunch of bug fixes and enhancements, as well as some fixes for XSS issues and a Jetty CVE.

The codename for Horizon 28.0.2 is [Soundwave](https://wikipedia.org/wiki/Soundwave_%5C(Transformers%5C)).

For a high-level overview of what has changed in Horizon 28, see [What’s New in OpenNMS Horizon 28](https://docs.opennms.com/horizon/28.0.2/releasenotes/whatsnew.html).

### A Note About Meridian 2018 and End of Life

This release marks 3 years of Meridian 2018, initially launched in September of 2018, so it is officially at its end of life as a supported release.  
If you haven't already upgraded, consider this our strong encouragement to do so. :D

Additionally, here is the EOL schedule for the newer Meridian releases:

- Meridian 2019 will expire in October of 2022
- Meridian 2020 will expire in September of 2023
- Meridian 2021 will expire in April of 2024

### Meridian Point Releases

All Meridian releases this month contained security updates, so it is recommended that you upgrade.

Additionally, 2020.1.11 adds a fix for a potential OOM on the Minion if off-heap storage is enabled for forwarding.

On top of that, 2021.1.3 adds documentation fixes, and a performance enhancement to the node cache used when processing flows.

For a list of changes, see the release notes:

- [2018.1.31](https://meridian.opennms.com/releasenotes/2018/latest/#releasenotes-changelog-Meridian-2018.1.31) ([_Typhoon_](https://wikipedia.org/wiki/Typhoon))
- [2019.1.22](https://meridian.opennms.com/releasenotes/2019/latest/#releasenotes-changelog-Meridian-2019.1.22) ([_Ugarit_](https://wikipedia.org/wiki/HD_218566))
- [2020.1.11](https://meridian.opennms.com/releasenotes/2020/latest/#releasenotes-changelog-Meridian-2020.1.11) ([_Ayre_](https://wikipedia.org/wiki/Ayre_%5C(landform%5C)))
- [2021.1.3](https://docs.opennms.com/meridian/2021.1.3/releasenotes/changelog.html#releasenotes-changelog-Meridian-2021.1.3) ([_MESSENGER_](https://wikipedia.org/wiki/MESSENGER))

### September Releases

<!--
git log --no-merges meridian-2016.1.23-1..origin/release-2016.x -- . ":(exclude).circleci"
-->

OpenNMS is on a monthly release schedule, with releases happening on the second Wednesday of the month.

The next OpenNMS release day is September 8th, 2021.

We currently expect a Horizon 28.0.3 release.

### Next Horizon: 29 (Q4 2021)

The next major Horizon release will be Horizon 29.

The current roadmap for Horizon 29 includes the following goals:

- running as non-root by default
- refactor the Minion's communication to get rid of out-of-band ReST calls to the OpenNMS core
- add support for persistence of flows to Cortex
- start the groundwork for replacing the topology UI with a pure-javascript version

### Next Meridian: 2022 (Q? 2022)

With Meridian 2021 recently out, we do not yet have a specific timeline for Meridian 2022.

Expect it to include -- at the very least -- the JDK11 requirement and flow aggregation improvements from Horizon 28.  
Ideally it will contain work going into Horizons 29 (and probably 30) if our timeline holds. ![😅](https://s.w.org/images/core/emoji/13.1.0/72x72/1f605.png)

### Disclaimer

_Note that this is just based on current plans; dates, features, and releases can change or slip depending on how development goes._

_The statements contained herein may contain certain forward-looking statements relating to The OpenNMS Group that are based on the beliefs of the Group’s management as well as assumptions made by and information currently available to the Group’s management. These forward-looking statements are, by their nature, subject to significant risks and uncertainties._

_...We apologize for the excessive disclaimers. Those responsible have been sacked._

_Mynd you, møøse bites Kan be pretti nasti..._

_We apologise again for the fault in the disclaimers. Those responsible for sacking the people who have just been sacked have been sacked._

<!--
## Calendar of Events
### **[OpenNMS Training](https://hs.opennms.com/training-registration-2020) - Moonachie, New Jersey - April 27th through May 1st, 2020**
The OpenNMS Group [still hopes to be offering training](https://hs.opennms.com/training-registration-2020) 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 Time…

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](mailto:twio@opennms.org).

- Ben

<!--
  https://github.com/OpenNMS/twio-fodder/blob/ee50b0f05f3f93a66c242448a70fdca3993b972a/scripts/twio-issues-list.pl
-->

## Resolved Issues Since Last OOH

- [NMS-7241](https://issues.opennms.org/browse/NMS-7241): Enhance geographical map to work with openstreetmap offline map
- [NMS-13282](https://issues.opennms.org/browse/NMS-13282): Nephron RandomFlowIT flaps in CircleCI
- [NMS-13422](https://issues.opennms.org/browse/NMS-13422): Add the full trap oid for v2 snmp event
- [NMS-13436](https://issues.opennms.org/browse/NMS-13436): Docker not able to access etc overlay as non-root
- [NMS-13451](https://issues.opennms.org/browse/NMS-13451): GeoMap: Temporary use existing OpenNMS RESTful APIs to get some real data
- [NMS-13454](https://issues.opennms.org/browse/NMS-13454): Geo-map: use Vuex to manage nodes info retrieved from OpenNMS
- [NMS-13462](https://issues.opennms.org/browse/NMS-13462): Implement In-memory broker for Object replication ( Twin)
- [NMS-13478](https://issues.opennms.org/browse/NMS-13478): Changes to review bulk indexing with raw flow data
- [NMS-13481](https://issues.opennms.org/browse/NMS-13481): Optimize node cache refresh to be non-blocking to flow data
- [NMS-13486](https://issues.opennms.org/browse/NMS-13486): Minions > v27.0.0 stop processing flows after apprx 5 minutes
- [NMS-13501](https://issues.opennms.org/browse/NMS-13501): IFTTT integration not working anymore