Planet OpenNMS

January 12, 2023

How to Monitor Processes With SNMP

Monitoring processes that don't provide network services is a default use case in network monitoring. Because they aren't providing network services, black box testing won't work- you need an agent on your system providing an inside view of your operating system. The Net-SNMP agent is easy to install and configure on Linux or Unix. It's compatible with any monitoring solution that supports SNMP, such as OpenNMS.

By default, there are basically two methods utilizing Net-SNMP:

  1. Using the HOST-RESOURCES-MIB
  2. Using the UCD-SNMP-MIB. Both are supported by the Net-SNMP agent.

Both methods produce the same result, but each will impact your monitoring system configuration and maintenance differently.

To help you decide which method to use, this article will discuss the costs and benefits for each. In this example, we'll discuss different monitoring solutions for two single processes as well as a multiprocess application.

Using the Host Resources MIB

When you're using the Host Resources MIB, the key information is in two tabular objects: the hrSWRunName and the according hrSWRunStatus.

In OpenNMS, you can use the HostResourceSwRunMonitor.

The key parameters are:

  • service-name: The name of the process you want to monitor from the hrSWRunName object
  • match-all: In case there are multiple processes running, all processes need to be in the named run-level state
  • run-level: The status of the process status, by default it is set to 2 and does not need to be changed

A typical SNMP output:

snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.2.1.25.4.2.1.2

.1.3.6.1.2.1.25.4.2.1.2.895 = STRING: "dockerd"

.1.3.6.1.2.1.25.4.2.1.2.938 = STRING: "tincd"

.1.3.6.1.2.1.25.4.2.1.2.1416 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1428 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1635 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1761 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1880 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1902 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1916 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1928 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1941 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1954 = STRING: "docker-proxy"

.1.3.6.1.2.1.25.4.2.1.2.1972 = STRING: "docker-proxy"

snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.2.1.25.4.2.1.7

.1.3.6.1.2.1.25.4.2.1.7.895 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.938 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1416 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1428 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1635 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1761 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1880 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1902 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1916 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1928 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1941 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1954 = INTEGER: runnable(2)

.1.3.6.1.2.1.25.4.2.1.7.1972 = INTEGER: runnable(2)

For each process you want to monitor, you have to create a service monitor named something like Process-docker-proxy, Process-tincd and Process-dockerd.

Pros: It allows you to set up granular monitoring for every process. The service monitors can be used in "Service Level Management" on the start page for availability calculation and notifications for each process.

Cons: You have to configure and maintain a service monitor for each process you want to monitor in OpenNMS. It is not possible to configure something like: "At least a number x of y processes need to be running to have the service to be ok."

Using the UCD-SNMP-MIB

Net-SNMP has a mechanism to monitor processes on the system with the proc directive in the configuration file. The proc directive is pretty easy to configure:

proc docker-proxy 20 5

The first argument is the name of the process you want to monitor—in this case the process named docker-proxy. To be safe, you should run at least 5, but not more than 20 processes named docker-proxy. The maximum and minimum number of processes is optional. And when they don't exist, at least one process should be running to be okay.

If you'd like to use a configuration management tool to configure your SNMP agent, in snmpd.conf, you can use the:

includeDir /etc/snmp/conf.ddirective

That way you can drop a .conf file with the proc directive for each application you want to monitor, and each will be included.

An example for monitoring tincd, dockerd, and docker-proxy with the configured proc looks like the following:

Name of the process
  
snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.4.1.2021.2.1.2
iso.3.6.1.4.1.2021.2.1.2.1 = STRING: "tincd"
iso.3.6.1.4.1.2021.2.1.2.2 = STRING: "dockerd"
iso.3.6.1.4.1.2021.2.1.2.3 = STRING: "docker-proxy"
  
Number of instances
  
snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.4.1.2021.2.1.5
iso.3.6.1.4.1.2021.2.1.5.1 = INTEGER: 3
iso.3.6.1.4.1.2021.2.1.5.2 = INTEGER: 1
iso.3.6.1.4.1.2021.2.1.5.3 = INTEGER: 13
  
Error messages
  
snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.4.1.2021.2.1.101
iso.3.6.1.4.1.2021.2.1.101.1 = ""
iso.3.6.1.4.1.2021.2.1.101.2 = ""
iso.3.6.1.4.1.2021.2.1.101.3 = ""
  
Error flags
  
snmpwalk -v 2c -c useVersion3 localhost .1.3.6.1.4.1.2021.2.1.100
iso.3.6.1.4.1.2021.2.1.100.1 = INTEGER: 0
iso.3.6.1.4.1.2021.2.1.100.2 = INTEGER: 0
iso.3.6.1.4.1.2021.2.1.100.3 = INTEGER: 0
  

The PrTableMonitor uses the tables above to monitor the status of running processes. There are no specific configuration parameters necessary, because the configuration of how and which processes are monitored is located in the Net-SNMP configuration.

In OpenNMS, configure just one monitor named something like Process-Table. As soon as the Net-SNMP agent identifies a process is not running in the specified boundaries, the Error Flag table is updated and is changed from 0 to 1. The OpenNMS monitor will populate a list of names with the processes that are not in a desired state.

Pros: You have only to configure one PrTable Monitor in OpenNMS, regardless of how many processes you want to monitor. The detailed configuration of which process needs to be monitored is configured on the monitored system itself; the SNMP agent needs to be configured anyway, and configuration management tools are in place in larger environments. It is possible to configure in detail how many processes and which processes need to be monitored. Only one service goes down if multiple processes fail.

Cons: There is only one service in OpenNMS for all services, it is not possible to notify different people for specific processes. In case you have one process that fails and the monitor goes down and a second process fails, the event reason in OpenNMS documents only the event reason for the initial process failure.

The post How to Monitor Processes With SNMP appeared first on The OpenNMS Group, Inc..

by Ronny at January 12, 2023 12:00 AM

January 11, 2023

January 2023 Releases – Horizon 31.0.3, Meridian 2022.1.11, 2021.1.23, 2020.1.31

In January, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 31.0.3.

Meridian Stable Updates

Meridians 2020.1.31 , 2021.1.23 , and 2022.1.11 contains a handful of bug and security fixes, and a cosmetic change to the web UI.

For a list of changes, see the release notes:

Horizon 31.0.3

Release 31.0.3 is a minor release which fixes a number of UI and backend bugs, brings one small UI enhancement, patches two potential security vulnerabilities, and formalizes support for RHEL 9 and PostgreSQL 15.

For a high-level overview of what has changed in Horizon 31, see What’s New in OpenNMS Horizon 31.

For a complete list of changes, see the changelog.

The codename for Horizon 31.0.3 is Biscotti.

The post January 2023 Releases – Horizon 31.0.3, Meridian 2022.1.11, 2021.1.23, 2020.1.31 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at January 11, 2023 04:01 PM

OpenNMS Horizon 31.0.3 (Biscotti)

Release 31.0.3

Release 31.0.3 is a minor release which fixes a number of UI and backend bugs, brings one small UI enhancement, patches two potential security vulnerabilities, and formalizes support for RHEL 9 and PostgreSQL 15.

The codename for Horizon 31.0.3 is Biscotti.

Task
  • Geo Map: Add content to the map marker pop up (Issue NMS-13698)
  • Uncontrolled Resource Consumption in Jackson-databind (Issue NMS-15030)
  • Add flow version table to Flow Introduction (Issue NMS-15158)
  • Change OpenNMS Copyright from 2022 to 2023 (Issue NMS-15211)
  • Change OpenNMS Copyright from 2022 to 2023 in the documentation footer (Issue NMS-15212)
Enhancement
  • Include Minion version on "Manage Minions" page (Issue NMS-14493)
  • Update docs to include RHEL 9 install instructions (Issue NMS-15147)
  • Test and Document Support for PostgreSQL 15 (Issue NMS-15151)
Bug
  • RRD persistence with default configs in our Horizon OCI points to wrong libjrrd2.so (Issue NMS-14778)
  • Chrome/Edge Web Browser : Geographical Map Node Counters are wrong (Issue NMS-14792)
  • Form Resubmission From Cache (Issue NMS-14933)
  • Web UI menu item "Endpoints" not in best location (Issue NMS-15004)
  • Incorrect labels on OpenNMS-JMX collection resource types (Issue NMS-15044)
  • Snmp collect reversing to unticked after a few hours (Issue NMS-15117)
  • Log Out does not work from new nav-bar menu (Issue NMS-15119)
  • reloading BSM daemon causes the state of serviceProblem alarm to be reset (Issue NMS-15124)
  • Vue Menubar items obscured by Geo Map (Issue NMS-15149)
  • Flows adapters don’t start on Sentinel running as a container. (Issue NMS-15161)
Epic
  • Formalize support for RHEL 9 and its derivatives (Issue NMS-14897)
Story
  • Fix smoke test for new UI (Issue NMS-14910)
  • Add JSON support (in additional to GBP) to the Kafka producer for flows (Issue NMS-15027)
  • publish opennms-plugin-cloud 1.0.6 (Issue NMS-15142)

by mershad-manesh at January 11, 2023 03:48 PM

December 17, 2022

December 14, 2022

December 2022 Releases – Horizon 31.0.2, Meridian 2022.1.10, 2021.1.22, 2020.1.30

In December, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 31.0.2.

Meridian Stable Updates

Meridians 2020.1.30 , 2021.1.22 , and 2022.1.10 contains a handful of bug and security fixes, and a couple of back-ported enhancements.

For a list of changes, see the release notes:

Horizon 31.0.2

Release 31.0.2 is a minor release which fixes a great many bugs and security vulnerabilities, updates the versions of many library dependencies, and introduces some enhancements related to Minion Appliances.

The official documentation has also received significant improvements.

NOTE: The documentation for enabling JAAS encryption for Minion and Sentinel has changed. If you have enabled encryption previously and wish to enable stronger Jasypt-based encryption, you need to reset any existing user passwords.

For a high-level overview of what has changed in Horizon 31, see What’s New in OpenNMS Horizon 31.

For a complete list of changes, see the changelog.

The codename for Horizon 31.0.2 is Stroopwafel.

The post December 2022 Releases – Horizon 31.0.2, Meridian 2022.1.10, 2021.1.22, 2020.1.30 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at December 14, 2022 04:12 PM

OpenNMS Horizon 31.0.2 (Stroopwafel)

Release 31.0.2

Release 31.0.2 is a minor release which fixes a great many bugs and security vulnerabilities, updates the versions of many library dependencies, and introduces some enhancements related to Minion Appliances. The official documentation has also received significant improvements.

The documentation for enabling JAAS encryption for Minion and Sentinel has changed. If you have enabled encryption previously and wish to enable stronger Jasypt-based encryption, you need to reset any existing user passwords.

The codename for Horizon 31.0.2 is Stroopwafel.

Bug
  • Failures when jaeger tracing is enabled on Core server and Minion (Issue NMS-14550)
  • Missing /run/opennms on Ubuntu (Issue NMS-14650)
  • javadoc not being generated in H31 (Issue NMS-14750)
  • OpenNMS opennms start fails on Ubuntu (Issue NMS-14838)
  • Regression: install script fails if an OpenNMS directory contains root-owned lost+found directory (Issue NMS-14919)
  • No /var/lib/opennms on 30.0.4 Docker image (Issue NMS-14976)
  • XML Entity Expansion Injection in geolocation API (Issue NMS-14988)
  • UI Preview: UI Plugins do not work if multiple are installed (Issue NMS-14996)
  • OIA Pollers non-functional (Issue NMS-15001)
  • Web UI menu item "Endpoints" not in best location (Issue NMS-15004)
  • Icon for admin menu items missing from some items (Issue NMS-15005)
  • Remove reference to remote pollers (Issue NMS-15017)
  • Lock contention in SnmpPeerFactory (Issue NMS-15042)
  • opennms rpm could get wrong jetty files (Issue NMS-15043)
  • Horizon Karaf container not healthy after installing opennms-timeseries-api with opennms-plugins-cortex-tss (Issue NMS-15078)
  • RHEL9/CentOS9/Rocky 9 need chkconfig package to enable service properly (Issue NMS-15093)
  • Default limit of 10 is not working for event queries (Issue NMS-15123)
Enhancement
  • Dependabot: leaflet from 1.7.1 to 1.8.0 (Issue NMS-14584)
  • Error compiling Cisco MIB (Issue NMS-14640)
  • Doc update: Enable salted hash passwords within Karaf for core/Minion/Sentinel (Issue NMS-14736)
  • Add "admin" disambiguation to Glossary (Issue NMS-14914)
  • simplify docker tags in H31+ (Issue NMS-14989)
  • Update Debian/Ubuntu Upgrade Instructions (Issue NMS-15087)
  • dependabot: Upgrade PostgreSQL dependency to 42.4.3 (or higher) (Issue NMS-15095)
  • Update style elements in Quick Start guide (Issue NMS-15106)
Unexpected Behavior
  • RPM packages fail to install when FIPS Enabled (Issue NMS-14628)
Story
  • Upgrade AngularJS to latest 1.x (Issue NMS-14715)
  • Apache Log4j 1.x Multiple Vulnerabilities (PB-2022, Sep 2022) (Issue NMS-14818)
  • Modify foreign source in HeartbeatConsumer to ignore docker interfaces and detect SNMP agent (Issue NMS-14855)
  • OpenShift test coverage (Issue NMS-14882)
  • SNMP Community retrieval through SCV on Minion (Issue NMS-15008)
  • Add JSON support (in additional to GBP) to the Kafka producer for flows (Issue NMS-15027)
  • Backport deploy-base update from develop to release-31.x (upgrades JRE minor version, adds vim-tiny, less) (Issue NMS-15046)
  • Add KPI for Appliance count by model (Issue NMS-15051)
Task
  • Quick Start: "Beyond Quick Start" chapter (Issue NMS-14735)
  • H31 Release testing (Issue NMS-14797)
  • Review enlinkd documentation (Issue NMS-14850)
  • Update Visualization topic in Quick Start guide (Issue NMS-15029)
  • Fix Antora version differences (Issue NMS-15088)
  • Update opennms-plugin-cloud to 1.0.4 (Issue NMS-15122)

by mershad-manesh at December 14, 2022 03:59 PM

November 16, 2022

November 2022 Releases – Horizon 31.0.1

Horizon 31.0.1

Release 31.0.1 is a small out-of-band release to address some issues found during 31.0.0 testing.

It contains a few small changes including a fix for unusually large docker images and some other small bug fixes,
as well as some updates to the new Quick Start Guide and a fix to the installation instructions for the Cortex plugin.

Please note there is a known issue that only one plugin entry shows up in the navigation bar's "Plugins" menu, even if multiple plugins are installed.
Only ALEC users who install the cloud connector are impacted.
ALEC users therefore should avoid the Cloud Services Connector plugin until a new release fixes the underlying bug.

For a high-level overview of what has changed in Horizon 31, see What’s New in OpenNMS Horizon 31.

For a complete list of changes, see the changelog.

The codename for Horizon 31.0.1 is Oreo.

See the differences between Horizon and Meridian.

The post November 2022 Releases – Horizon 31.0.1 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at November 16, 2022 09:51 PM

OpenNMS Horizon 31.0.1 (Oreo)

Release 31.0.1

Release 31.0.1 is a small out-of-band release to address some issues found during 31.0.0 testing.

It contains a few small changes including a fix for unusually large docker images and some other small bug fixes, as well as some updates to the new Quick Start Guide and a fix to the installation instructions for the Cortex plugin.

Please note there is a known issue that only one plugin entry shows up in the navigation bar’s "Plugins" menu, even if multiple plugins are installed. Only ALEC users who install the cloud connector are impacted. ALEC users therefore should avoid the Cloud Services Connector plugin until a new release fixes the underlying bug.

The codename for Horizon 31.0.1 is Oreo.

Bug
  • OpenAPI Validation Errors (Issue NMS-14408)
  • Snmp Polling Status shows Polled even though it’s actually not (Issue NMS-14653)
  • Duplicated message when alarm is not found (Issue NMS-14686)
  • Errors while installing opennms-timeseries-api from karaf shell (Issue NMS-14874)
  • When you delete/put memo or journal it always returns 204 even if alarm not exists (Issue NMS-14901)
  • NoSuchElementException errors thrown by EnhancedLinkd (Issue NMS-14912)
  • Docs for Cortex plugin are incorrect (Issue NMS-14945)
  • Horizon/Sentinel docker image size ballooned (Issue NMS-15006)
  • HZN 31: Ubuntu installation issues (Issue NMS-15007)
Story
  • Quick Start: Review entire quick start section when complete. (Issue NMS-14721)
  • New UI Preview: Ensure ALEC UI works (Issue NMS-14891)
Task
  • Update Quick Start login chapter (Issue NMS-14984)
  • Update notifications.adoc in Quick Start section (Issue NMS-14985)
  • Update Quick Start notifications configuration chapter (Issue NMS-14999)

by mershad-manesh at November 16, 2022 09:42 PM

November 09, 2022

November 2022 Releases – Horizon 31.0.0, Meridians 2022.1.9, 2021.1.21, 2020.1.29, 2019.1.40

In November, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 31.0.0.

Meridian Stable Updates

Meridians 2019.1.40, 2020.1.29 , 2021.1.21 , and 2022.1.9 contains a handful of bug and security fixes, and a couple of back-ported enhancements.

For a list of changes, see the release notes:

Horizon 31.0.0

Release 31.0.0 is a new major release.

It contains several new features, including the Cloud Services Connector with Time Series DB support and a new quick-start guide.

Notable enhancements include integration of the Horizon 30 "UI Preview" items into the main UI and performance improvements to network topology discovery.
It also includes an important bug fix correcting a regression that rendered Horizon 30 unable to run in OpenShift environments, besides many other important bug and security fixes.

For a high-level overview of what has changed in Horizon 31, see What’s New in OpenNMS Horizon 31.

For a complete list of changes, see the changelog.

The codename for Horizon 31.0.0 is Doppelkeks.

The post November 2022 Releases – Horizon 31.0.0, Meridians 2022.1.9, 2021.1.21, 2020.1.29, 2019.1.40 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at November 09, 2022 04:51 PM

October 27, 2022

2022 Cybersecurity Awareness Month

October’s Cybersecurity Awareness Month seems like a great time to discuss the improvements we are making at The OpenNMS Group to improve our security practices.

For almost 20 years, OpenNMS staff developers and the open source contributor community have partnered to create robust and secure network monitoring platforms available in community-driven (Horizon) and enterprise-ready (Meridian) distributions..

Because OpenNMS deployments have access to sensitive network data within organizations, our developers have always diligently watched for security issues and responded quickly to address significant problems when needed. Security at OpenNMS was collectively “owned” by everyone.

In 2021, I joined OpenNMS as Chief Information Security Officer and began formalizing our security program. Although I still want security as part of everyone’s job, I also wanted our new security team to align our security program to industry standard practices, by making the following improvements:

  • Adopt the ISO/IEC 27001/2 Information security, cybersecurity, and privacy protection framework for the OpenNMS Security Program.
  • Create new Information Security Standards (“rules”) aligned to ISO. We completed phase one in June 2022.
  • Revise our internal software development, operations, and business processes to better align to our new security standards and ISO. We expect to complete this phase two work by year-end 2022.
  • In 2023, we will conduct an audit of our security program to ensure alignment to security best practices as described in ISO 27001/2.
  • Updated our privacy practices to ensure compliance with GDPR and CCPA privacy regulations.
  • OpenNMS recently became a CVE numbering authority (CNA) so that we can now feed vulnerability remediation information into the global CVE database maintained by the non-profit MITRE Corporation. This allows our customers to use industry-standard tools to quickly detect and remediate reported vulnerabilities within our software.
  • Engaged an outside firm to increase security penetration testing for our products and services. Previously all security testing was in-house or by the open-source community, which remain valuable sources of security testing.

We welcome any questions or feedback regarding these security improvements via email (security@opennms.com) or our customer support team. And thank you for using and contributing to OpenNMS projects and products.

Jeff Jancula, Chief Information Security Officer

The post 2022 Cybersecurity Awareness Month appeared first on The OpenNMS Group, Inc..

by Jeff Jancula at October 27, 2022 05:03 PM

October 17, 2022

Celebrate Open Source during Hacktoberfest 2022

Hacktoberfest is an annual, month-long celebration of open source software driven by Digital Ocean. During this event everyone can support open source by contributing changes, and earn some limited-edition swag.

We would like to invite you to participate and contribute to the OpenNMS project. There are many ways to contribute: you can work on code or documentation. Generally speaking, any pull request in our GitHub repositories qualifies.

How to contribute

First, visit the Hacktoberfest website to register for the event. Second, contribute to any open source project.

Our software is developed under AGPLv3 on GitHub. You are welcome to contribute to any repository in this organization. The procedure on how we manage and track issues and deal with pull requests is described in our how to contribute guide in our Discourse forum. You will also find information on how to connect with people in our community for further questions and help.

You can freely create an account in our JIRA. We have collected some issues (marked quickwin or quickwindoc) in our issue tracker that are reasonable candidates to claim for the event. Claim a ticket by assigning it to your user name and click the "Start Progress" button.

Feel free to join our Mattermost chat server and pop in to the OpenNMS Development channel if you have any questions or want some guidance on where to start.

Hack the planet!

The post Celebrate Open Source during Hacktoberfest 2022 appeared first on The OpenNMS Group, Inc..

by Ronny at October 17, 2022 08:00 PM

October 12, 2022

October 2022 Releases – Horizon 30.0.4, Meridians 2022.1.8, 2021.1.20, 2020.1.28, 2019.1.39

In October, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 30.0.4.

Meridian Stable Updates

Meridians 2019.1.39, 2020.1.28 , 2021.1.20 , and 2022.1.8 contains a handful of bug and security fixes, and a couple of back-ported enhancements.

For a list of changes, see the release notes:

Horizon 30.0.4

Release 30.0.4 contains quite a few bug and security fixes and a number of enhancements.

For a high-level overview of what has changed in Horizon 30, see What’s New in OpenNMS Horizon 30.

For a complete list of changes, see the changelog.

The codename for Horizon 30.0.4 is Capybara.

The post October 2022 Releases – Horizon 30.0.4, Meridians 2022.1.8, 2021.1.20, 2020.1.28, 2019.1.39 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at October 12, 2022 03:18 PM

October 03, 2022

OpenNMS On the Horizon – October 3rd, 2022

It's time once again for OpenNMS On the Horizon.

Since last time, we worked on documentation (SNMP poller, Trapd, Enlinkd, requisitions, quick start guide), Enlinkd refactoring, Docker container scanning, Horizon Stream (Keycloak integration, operator config, port forwarding, metrics, PostgreSQL auth, CI, Minion gateway, Kafka, docs, PagerDuty, ignite tests, Helm charts, UI navigation), event improvements, Sonar and code coverage, ALEC (API, test coverage, UI), tests (CI improvements, device config backup, logging), time-series off-heap support, provisioning, cookies and CSRF, JavaScript dependencies, Helm (AngularJS to React transition), and UI preview integration.

Github Project Updates

Internals, APIs, and Documentation
  • Mark Mahacek worked on SNMP poller and Trapd documentation
  • Antonio refactored some Enlinkd scheduling classes out into core/daemon
  • Morteza worked on Docker container security scanning
  • I worked on backporting Docker changes to foundation-2022
  • Gerald did more work on the Keycloak integration in Horizon Stream
  • Dmitri continued his work on poller config support in OPA
  • Antonio added some test coverage for Enlinkd startup
  • Antonio made a bunch of updates to Enlinkd documentation
  • Emily worked on a bunch of cleanups to the requisition docs
  • Jeffrey-David Kapp did a bunch of simplifications to operator config and port forwarding for Stream
  • Thomas started implementing datachoices metrics in Stream
  • Gerald enabled configuring PostgreSQL authentication in Stream
  • Jason continued his work on a CI pipeline for Stream
  • Łukasz and Mark Frazier did more work on the Minion gateway in Stream
  • Mark Mahacek worked on a number of event formatting and reduction key improvements
  • I worked on fixing up Sonar runs in foundation-2022 including supporting code coverage from smoke tests
  • James fixed some Kafka-related test failures in Stream
  • Ronny worked on some doc changes in Stream
  • Benjamin Janssens worked on adding and removing alarms from situations in ALEC
  • Mike Rose worked on the PagerDuty integration in Stream
  • Arthur worked on ignite integration in Stream test infrastructure
  • Bonnie worked on service availability info in the quick start guide
  • Emily worked on baseline and notifications docs in the quick start guide
  • I fixed some CI fallout from recent integration test container changes
  • Alexander worked on creating a device config backup smoke test
  • I fixed maven signing in the ALEC release CI
  • Gerald worked on helm chart improvements in Stream
  • Morteza worked on speeding up smoke tests by combining them in a single CircleCI job
  • I changed a bunch of AbstractMockDao logging to trace-level, it's way too chatty when running tests
  • Freddy worked on some buffering improvements in time-series off-heap caching
  • Sean fixed an issue with an NPE in provisioning when the web UI is run independent of the backend
Web, REST, UI, and Helm
  • Christian made some changes to default cookie handling and CSRF tokens for forms
  • I worked on modernizing some of our javascript dependencies
  • Chinh Le reworked the Horizon Stream navigation
  • Benjamin Janssens worked on test coverage for the ALEC UI
  • Anya worked on pagination and search in the ALEC UI
  • Rob did more work on fixing an add issue with limits in the location REST API
  • Scott worked on converting Helm's AngularJS components to React
  • Scott did some initial work to integrate the new UI and menu bar
Contributors

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

  • Chinh Le
  • Scott Theleman
  • Łukasz Dywicki
  • Benjamin Reed
  • Mark Frazier
  • Dmitri Herdt
  • Christian Pape
  • Sean Torres
  • Gerald Humphries
  • Anya Rybalova
  • Bonnie Robinson
  • Morteza Ershad-Manesh
  • Freddy Chu
  • Emily Marsh
  • Benjamin Janssens
  • Alexander Chadfield
  • Thomas Bigger
  • Scott Thompson
  • Mark Mahacek
  • Jeffrey-David Kapp
  • Arthur Naseef
  • Mike Rose
  • Rob Ellis
  • Antonio Russo
  • Alberto Ramos
  • James Hutchinson
  • Ronny Trommer
  • Jason Berry

Coming Soon: JIRA Migration

We will be migrating our JIRA issue-tracker from a self-hosted version to Atlassian's cloud version.
I don't have a timeline for this yet, but expect it in the coming months.

If you currently have an account at the OpenNMS issue tracker your account should already be migrated to JIRA Cloud, but you will need to perform a password reset with the "Can't log in?" link before you can log in.

Hacktoberfest

It's that time of year again!

Hacktoberfest 2022 has started, and it is once again time to make open source projects better and maybe get a t-shirt in the process. ;)

OpenNMS is participating and we've got a bunch of issues marked quickwin or quickwindoc in our issue tracker if you'd like to play along.

Feel free to join our Mattermost chat server and pop in to the OpenNMS Development channel if you have any questions or want some guidance on where to start.

Happy hacking!

Releases and Roadmap

Upcoming Releases

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

The next OpenNMS release day is October 12th, 2022.

We currently expect updates to all supported Meridians, plus Horizon 30.

Next Horizon: 31 (Q4 2022)

The next major Horizon release will be Horizon 31.

It will contain a number of improvements, including:

  • a refactoring of flow APIs including support for some flow hooks in the plugin API (plugin API 1.1.0+)
  • major improvements and refactoring in Enlinkd's bridge topology mapping and collection scheduling
  • a bunch of improved analytics in our datasources plugin
  • support for Hashicorp Vault in SCV
  • promoting a number of the "UI preview" enhancements to become part of the main UI
  • improvements to the requisitions REST API
  • a new Quick Start Guide in the documentation
Next Meridian: 2023 (Q1 2023)

Meridian 2023 is still reasonably early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.

Meridian 2019 EOL in November

Meridian releases are supported for 3 years.
The initial Meridian 2019 happened pretty late in the year, so its 3-year birthday will be November 6th, 2022.
The November 9th release cycle will be the final release as it rolls out of active support.

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

All Things Open - Raleigh, NC - October 30th through November 2nd, 2022

All Things Open is local to our headquarters, and is a truly fantastic event.
We love it so much, we will be the exclusive live stream sponsor. 😉

We'll also have a booth in the exhibition hall.
A bunch of OpenNMS folks will be attending and/or helping out in the booth, so please be sure to say hi!

Open Source Monitoring Conference - Nuremberg, Germany - November 14th through 16th

The OpenNMS Group is a gold sponsor of OSMC this year, and will have a booth as well.
Stop by and say hello!

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.

- Ben

Resolved Issues Since Last OOH

  • ALEC-142: Situation Storage: Implement situation storage to definite location.
  • ALEC-178: Sonar Cloud Security Grade A - Figure out What We Need to Fix and Report the List
  • ALEC-180: Investigate MIMIC to test ALEC
  • ALEC-183: Fix visual bugs - release 2.1.x
  • ALEC-191: Backend - Create endpoint to add/remove alarms from situation
  • HS-117: Release tags for Docker Images and Github
  • HS-127: Ingress update for latest k8s versions
  • HS-129: Allow for instance specific SSL certs
  • HS-140: Cleanup UI yaml and entrypoint.sh for hs ui image
  • HS-234: Add notifications GQL mutation when service is available
  • HS-282: Elasticsearch pod stuck pending
  • HS-310: Remove manual steps from dev environment setup
  • HS-339: Stats: Implement Phase 1 Metrics collection
  • HS-344: Grafana test and config for operator
  • HS-354: Expose notifications endpoints through GQL
  • HS-368: Strimzi Kafka memory usage
  • HS-370: Get ingress to use port 80, https as well.
  • HS-380: FE - Add store unit tests
  • HS-382: Keycloak realm import from Keycloak operator sometimes fails when deployed into Kind
  • HS-384: Error from first Keycloak realm import: "Key (name)=(master) already exists."
  • HS-395: Dynamic imports only work in local dev
  • HS-397: Research/prototype with different charting libraries
  • HS-402: Update and fix Vitest config to handle latest Featherds versions
  • HS-403: Repo cleanup: remove local-sample
  • HS-407: AlarmKafkaConsumerIntegrationTest.testProducingAlarmWithConfigSetup fails intermittently
  • HS-409: Convert any ConfigMaps that store sensitive info to Secrets
  • HS-410: Enable Postgres authentication
  • HS-411: Allow Operator to generate passwords with special characters
  • HS-412: Handle TLS properly across Helm chart
  • HS-416: Keycloak password is showing in Core logs
  • HS-420: Allow configuration of ingress port numbers in Operator/CRD
  • HS-423: UX competitive analysis on 5 competitors
  • NMS-9334: BSMAdminIT flapping
  • NMS-14125: Discourage and optimize use of cci build workspace
  • NMS-14397: EnhancedLinkd Collection priority Scheduling
  • NMS-14450: VMware requisition import fail with "Problem getting input stream: '{}'"
  • NMS-14520: Build MOS dashboard and supporting components
  • NMS-14539: Identify web UI styling quick wins
  • NMS-14593: Populate Velocloud Partner Requisition with Gateway Nodes
  • NMS-14617: Quick Start: Set up a threshold
  • NMS-14660: MOS CDR: Grafana/Helm Integration, display MOS data
  • NMS-14671: Add documentation for partial configuration modification via REST
  • NMS-14716: Form Can Be Manipulated with Cross-Site Request Forgery (CSRF)
  • NMS-14717: Session Cookie (Authentication Related) Does Not Contain The "HTTPOnly" Attribute
  • NMS-14724: backport CircleCI and Docker enhancements from develop to release-30.x
  • NMS-14729: Add new handling options for the snmp provisioning metadata adapter
  • NMS-14731: Can the OG nav-bar coexist with a Feather / Vue app?
  • NMS-14740: Kafka Producer NPE causes collection failure overall
  • NMS-14763: Add Priority Executor Classes
  • NMS-14771: Move Common Adapter Enlinkd classes to Core
  • NMS-14772: Implement connection manager
  • NMS-14773: Provide SubNetwork Classes for Enhanced Linkd
  • OIA-45: OIA Add interface for poller-configuration

The post OpenNMS On the Horizon – October 3rd, 2022 appeared first on The OpenNMS Group, Inc..

by RangerRick at October 03, 2022 07:47 PM

September 26, 2022

OpenNMS On the Horizon – September 26th, 2022

It's time once again for OpenNMS On the Horizon.

Since last time, we worked on pyroscope profiling, CircleCI improvements, documentation (Grafana dashboard, Quick Start guide, Trapd, graphQL notification query, requisition REST), Horizon Stream (Minion gateway and heartbeat, operator improvements, JMX, Helm charts, PagerDuty, discovery), Sonar bug fixes, OPA (Poller Config and time-series offheap persistence), SNMPv3 traps, Enlinkd, Graphite time-series, smoke tests, flow classification, Provisiond config validation, SNMP metadata provisioning, Helm improvements, ALEC UI, startup progress bar, and web form fixes.

Github Project Updates

Internals, APIs, and Documentation
  • DJ worked on adding support for Pyroscope profiling
  • Morteza tested out reducing build container sizes for RPM/Debian builds
  • Morteza worked on cleaning up some output in the dynamic config scripts
  • Mark Mahacek worked on the grafana dashboard docs
  • Bonnie and Emily did more work on the quick start guide including performance data, system baseline, and thresholding info
  • Morteza fixed some issues in experimental build triggering in dynamic config
  • Mark Frazier did some more work on the Minion gateway in Horizon Stream
  • Yang Li worked on bringing some JMX code over to Stream
  • Gerald did some more work on Helm charts in Stream
  • I worked on cleaning up some leftover Sonar stuff from DevJam
  • Łukasz continued his work on twin/RPC for the Minion gateway
  • Arthur worked on some SNMP utility and testing code in Stream
  • Emily cleaned up the JDK references and some other formatting in the deployment guide
  • Jeffrey-David Kapp worked on some namespace code for the Keycloak operator in Stream
  • I fixed the ActiveMQ initialization to happen lazily so it doesn't yell if not configured
  • James updated the Stream PagerDuty integration to attach alarm details to the payload
  • Chandra continued his work on discovery in Stream
  • Dmitri worked on poller config support in OPA
  • Freddy continued to work on OPA time-series persistence
  • Arthur and Mark Frazier added Minion heartbeat processing in Stream
  • Alex implemented no-op message processors for ignoring spurious chunks in SNMPv3 traps
  • Bonnie added Trapd to the daemon reference
  • I did a bunch of optimization work in our CircleCI pipeline to reduce network usage
  • Antonio refactored the NetworkBuilder used in Enlinkd tests
  • Antonio worked on Enlinkd per-protocol scheduling intervals
  • Alexander worked on fixing the flapping BSM admin integration test
  • Thomas worked on usage statistics in Stream
  • Dustin did more work on flow classification improvements
  • Dmitri added some validation to Provisiond config loading
  • Scott improved the Graphite time-series adapter to support setting the node in groovy scripts
  • Antonio updated our InetAddress tools to include some Netmask-related utility functions
  • Gerald refactored a bunch of configs related to startup in Stream
  • Sean added support for keeping some metadata when the SNMP provisioning adapter runs
  • Jason Berry worked on a bunch of Horizon Stream CI/CD improvements
  • Morteza worked on security scanning our Docker images when we build them
  • DJ implemented a startup progress bar
  • Antonio worked on an improved bridge topology algorithm in Enlinkd
Web, REST, UI, and Helm
  • I cleaned up some branch merge and other CircleCI stuff in Helm
  • Chinh Le worked on the Horizon Stream events table
  • I worked on updating some dependencies in our JavaScript build
  • Anya worked on filtering in the ALEC UI, as well as some bug cleanup
  • Mike Rose fixed up some UI dynamic import code in Stream
  • Christian added CSRF tokens to a bunch of web forms
  • James added graphQL support for notification queries in Stream
  • Emily updated the requisition REST documentation
Contributors

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

  • Antonio Russo
  • DJ Gregor
  • Emily Marsh
  • Arthur Naseef
  • Benjamin Reed
  • Bonnie Robinson
  • Jason Berry
  • Morteza Ershad-Manesh
  • Yang Li
  • Łukasz Dywicki
  • Mark Frazier
  • Freddy Chu
  • Benjamin Janssens
  • Dmitri Herdt
  • James Hutchinson
  • Christian Pape
  • Chinh Le
  • Sean Torres
  • Dustin Frisch
  • Gerald Humphries
  • Chandra Gorantla
  • Scott Theleman
  • Anya Rybalova
  • Mark Mahacek
  • Mike Rose
  • Alexander Chadfield
  • Jeffrey-David Kapp
  • Thomas Bigger
  • Alex May
  • Rob Ellis
  • Patrick Schweizer

Coming Soon: JIRA Migration

We will be migrating our JIRA issue-tracker from a self-hosted version to Atlassian's cloud version.
I don't have a timeline for this yet, but expect it in the coming months.

If you currently have an account at the OpenNMS issue tracker your account should already be migrated to JIRA Cloud, but you will need to perform a password reset with the "Can't log in?" link before you can log in.

Releases and Roadmap

Upcoming September Releases

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

The next OpenNMS release day is October 12th, 2022.

We currently expect updates to Horizon 30.

Next Horizon: 31 (Q4 2022)

The next major Horizon release will be Horizon 31.

It will contain a number of improvements, including:

  • a refactoring of flow APIs including support for some flow hooks in the plugin API (plugin API 1.1.0+)
  • major improvements and refactoring in Enlinkd's bridge topology mapping and collection scheduling
  • a bunch of improved analytics in our datasources plugin
  • support for Hashicorp Vault in SCV
  • promoting a number of the "UI preview" enhancements to become part of the main UI
  • improvements to the requisitions REST API
  • a new Quick Start Guide in the documentation
Next Meridian: 2023 (Q1 2023)

Meridian 2023 is still reasonably early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.

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

All Things Open - Raleigh, NC - October 30th through November 2nd, 2022

All Things Open is local to our headquarters, and is a truly fantastic event.
We love it so much, we will be the exclusive live stream sponsor. 😉

We'll also have a booth in the exhibition hall.
A bunch of OpenNMS folks will be attending and/or helping out in the booth, so please be sure to say hi!

Open Source Monitoring Conference - Nuremberg, Germany - November 14th through 16th

The OpenNMS Group is a gold sponsor of OSMC this year, and will have a booth as well.
Stop by and say hello!

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.

- Ben

Resolved Issues Since Last OOH

  • HELM-346: Docs for 8.0.1 did not publish
  • HS-249: Grafana support in the Operator
  • HS-252: Stabilize local-sample/ & Sync It with Skaffold Build
  • HS-318: GeoMap and Topology Contextual Actionable Intelligence LF Wireframes
  • HS-337: Stats: Create platform module for data choices
  • HS-338: Stats: Make REST call to post data choices to UsageStatsHandler
  • HS-362: FE - Add events and metric to device page
  • HS-363: FE - Use widget to display device event table
  • HS-364: Auto update config to subscribed modules
  • HS-366: Single Keycloak operator instance
  • HS-369: Once opennms/horizon-stream-notification repo has been added to Dockerhub, create a github actions pipeline to publish it
  • HS-379: Add Event Driven Discovery for Trapd
  • HS-394: Notifications: Add alarm to custom details
  • HS-396: Migrate and save JMX config in Json config store.
  • NMS-12629: Trapd is missing in the docs
  • NMS-14158: provide documentation for DCB feature
  • NMS-14220: Leaflet geo-map bug roundup
  • NMS-14221: H30 upgrades should not hurt
  • NMS-14222: Things that need updating to work well with Grafana 8.x
  • NMS-14223: Dependencies that need upgrading in H30
  • NMS-14241: Enable authorized web users to edit config files in OPENNMS_HOME/etc
  • NMS-14251: Make sure the DCB config files are in working order
  • NMS-14647: Cortex TSS release prep
  • NMS-14659: MOS CDR Processor: Tie to node
  • NMS-14670: DCB fails on newly provisioned nodes
  • NMS-14672: Velocloud API v1 / v2 support
  • NMS-14711: Release Work (September)
  • NMS-14718: Duplicate V3 trap security names causing spurious errors on non V3 traps
  • NMS-14752: On saving of the provisiond configuration must be ensured, that all requsition-def's have unique names
  • NMS-14756: Update QS based on ONMSU feedback
  • NMS-14762: Refactor Enlinkd Test NetworkBuilder Class
  • NMS-14764: Set Up Enlinkd schedule time interval based on protocols
  • NMS-14770: MOS CDR Processor: Send to multiple OpenNMS instances
  • NMS-14774: Add network/netmask tools to InetAddressUtils
  • NMS-14775: Ability to Assign Device Configuration Backup to Foreign Source

The post OpenNMS On the Horizon – September 26th, 2022 appeared first on The OpenNMS Group, Inc..

by RangerRick at September 26, 2022 10:18 PM

September 21, 2022

OpenNMS.js v2.5.1

2.5.1 is a small release with just dependency updates, most notably moment.js and moment-timezone, plus minor bumps to Grafana dependencies.

What's Changed

  • build(deps-dev): bump typescript from 4.8.2 to 4.8.3 by @dependabot in #402
  • build(deps-dev): bump eslint from 8.23.0 to 8.23.1 by @dependabot in #403
  • build(deps-dev): bump @babel/preset-env from 7.19.0 to 7.19.1 by @dependabot in #404
  • build(deps): bump core-js from 3.25.0 to 3.25.2 by @dependabot in #406
  • build(deps-dev): bump @babel/plugin-transform-runtime from 7.18.10 to 7.19.1 by @dependabot in #407
  • build(deps): bump @babel/runtime-corejs3 from 7.19.0 to 7.19.1 by @dependabot in #408
  • build(deps-dev): bump typedoc from 0.23.14 to 0.23.15 by @dependabot in #409
  • build(deps-dev): bump @babel/core from 7.19.0 to 7.19.1 by @dependabot in #410
  • build(deps-dev): bump @antora/cli from 3.1.0 to 3.1.1 by @dependabot in #411
  • build(deps-dev): bump @antora/site-generator-default from 3.1.0 to 3.1.1 by @dependabot in #412

Full Changelog: v2.5.0...v2.5.1

by RangerRick at September 21, 2022 02:51 PM

September 19, 2022

OpenNMS On the Horizon – September 19th, 2022

It's time once again for OpenNMS On the Horizon.

Last week was DevJam, so keep that in mind when you get excited about some of the projects you see. ;)
Plenty of these are proof-of-concept work that may or may not make it into a release.

Anayway, since last time, we worked on Horizon Stream (Minion RPC and gateway, operator improvements, hashicorp vault support, device UI and events), documentation (quick start guide, grafana, flows), OpenTelemetry, VNC integration, Sonar (CI workflow, bug fixes), Enlinkd scheduling and OSPF area support, and hashicorp vault SCV integration (including REST).

Github Project Updates

Internals, APIs, and Documentation
  • DJ continued his work on moving from OpenTracing to OpenTelemetry
  • Łukasz did more work on Minion RPC in Horizon Stream
  • Arthur, Łukasz, and Mark continued the work on the Minion gateway in Stream
  • Thomas worked on a proof-of-concept VNC integration
  • Dmitri started to add support to OPA for adding poller config
  • Dustin did more work on twin API filter improvements
  • I worked on cleaning up our Sonar CI workflows(s)
  • Maxim, Benjamin Janssens, Ivan, Kim, and I worked on fixing issues detected by Sonar
  • Antonio continued his work on improving Enlinkd collection scheduling
  • Dustin and Freddy worked on adding support for flow processing to the Minion
  • Gerald did more work on operator workflow with Skaffold/Tilt in Stream
  • Jerry switched a bunch of Stream's configs to use hashicorp vault storage
  • Chandra worked on hashicorp vault support in SCV
  • I fixed a bug in our CircleCI integration test "changed project" detection that could cause it to build more than it needed to
  • Bonnie continued to work on improving the Quick Start Guide
  • Mark Mahacek worked on updated Grafana documentation
  • Alberto worked on adding OSPF area support to Enlinkd
  • Dino updated flow documentation
Web, REST, UI, and Helm
  • Chinh Le continued his work on the device UI and event display in Horizon Stream
  • Alex worked on a REST endpoint for SCV and vault config
Contributors

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

  • Dustin Frisch
  • Antonio Russo
  • Łukasz Dywicki
  • Mark Frazier
  • Benjamin Reed
  • Chinh Le
  • Freddy Chu
  • Chandra Gorantla
  • Arthur Naseef
  • Alberto Ramos
  • Maxim Brener
  • DJ Gregor
  • Christian Pape
  • Benjamin Janssens
  • Alex May
  • Dmitri Herdt
  • Ivan Trechekas
  • Thomas Bigger
  • Jerry Beuree
  • Dino Yancey
  • Mark Mahacek
  • Bonnie Robinson
  • Gerald Humphries
  • Emily Marsh

Coming Soon: JIRA Migration

We will be migrating our JIRA issue-tracker from a self-hosted version to Atlassian's cloud version.
I don't have a timeline for this yet, but expect it in the coming months.

If you currently have an account at the OpenNMS issue tracker your account should already be migrated to JIRA Cloud, but you will need to perform a password reset with the "Can't log in?" link before you can log in.

Releases and Roadmap

September 2022 Releases - Horizon 30.0.3, Meridians 2022.1.7, 2021.1.19, 2020.1.27, 2019.1.38

In September, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 30.0.3.

Meridian Stable Updates

Meridians 2019.1.38, 2020.1.27 , 2021.1.19 , and 2022.1.7 contains a couple of bug fixes.

For a list of changes, see the release notes:

Horizon 30.0.3

Release 30.0.3 contains quite a few bug fixes as well as number of small features and security fixes.

For a high-level overview of what has changed in Horizon 30, see What’s New in OpenNMS Horizon 30.

For a complete list of changes, see the changelog.

The codename for Horizon 30.0.3 is Chipmunk.

OpenNMS Helm 8.0.1

Helm 8.0.1 is primarily a bugfix release.

It contains a number of small fixes and enhancements to improve querying of nodes and interfaces.

It also contains a large number of node dependency updates.

Please note that Helm is still targeted to Grafana 8.
Work is underway to update to support Grafana 9.

Upcoming September Releases

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

The next OpenNMS release day is October 12th, 2022.

We currently expect updates to Horizon 30.

Next Horizon: 31 (Q4 2022)

The next major Horizon release will be Horizon 31.

It will contain a number of improvements, including:

  • a refactoring of flow APIs including support for some flow hooks in the plugin API (plugin API 1.1.0+)
  • major improvements and refactoring in Enlinkd's bridge topology mapping and collection scheduling
  • more stuff, which I haven't had a chance to go back and enumerate yet, watch this space :D
Next Meridian: 2023 (Q1 2023)

Meridian 2023 is still reasonably early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.

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

Grace Hopper Celebration - Orlando, FL - September 20th through 23rd

In addition to our involvement in Open Source Day, Veena Kannan will be presenting a virtual lightning talk at the Grace Hopper Conference titled "Open Source 101 – Myth Buster Edition" at the Grace Hopper Celebration.

Her talk will be Thursday the 22nd, at 11:00am.

All Things Open - Raleigh, NC - October 30th through November 2nd, 2022

All Things Open is local to our headquarters, and is a truly fantastic event.
We love it so much, we will be the exclusive live stream sponsor. 😉

We'll also have a booth in the exhibition hall.
A bunch of OpenNMS folks will be attending and/or helping out in the booth, so please be sure to say hi!

Open Source Monitoring Conference - Nuremberg, Germany - November 14th through 16th

The OpenNMS Group is a gold sponsor of OSMC this year, and will have a booth as well.
Stop by and say hello!

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.

- Ben

Resolved Issues Since Last OOH

  • NMS-12449: Remote Poller with Minion
  • NMS-13880: Deprecate Blackberry templates
  • NMS-14747: Error using javax.mail.* packages in plugins

The post OpenNMS On the Horizon – September 19th, 2022 appeared first on The OpenNMS Group, Inc..

by RangerRick at September 19, 2022 03:58 PM

September 14, 2022

September 2022 Releases – Horizon 30.0.3, Meridians 2022.1.7, 2021.1.19, 2020.1.27, 2019.1.38

In September, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 30.0.3.

Meridian Stable Updates

Meridians 2019.1.38, 2020.1.27 , 2021.1.19 , and 2022.1.7 contains a couple of bug fixes.

For a list of changes, see the release notes:

Horizon 30.0.3

Release 30.0.3 contains quite a few bug fixes as well as number of small features and security fixes.

For a high-level overview of what has changed in Horizon 30, see What’s New in OpenNMS Horizon 30.

For a complete list of changes, see the changelog.

The codename for Horizon 30.0.3 is Chipmunk.

The post September 2022 Releases – Horizon 30.0.3, Meridians 2022.1.7, 2021.1.19, 2020.1.27, 2019.1.38 appeared first on The OpenNMS Group, Inc..

by Morteza Ershad-Manesh at September 14, 2022 02:58 PM

September 12, 2022

OpenNMS On the Horizon – September 12th, 2022

It's time once again for OpenNMS On the Horizon.

Since last time, we worked on documentation (quick start guide, ALEC, partial config updates, cortex time-series), Horizon Stream (notifications, unit/integration test, ignite detector client, operator, Minion gRPC, Grafana, Keycloak, map UI, widgets, trap processing), SNMP metadata provisioning, ALEC (release work and UI), dynamic CI config, datachoices (notifications and outages, poller fixes), Enlinkd collection scheduling, Docker, offheap storage, dependabot updates, filter rules, Sonar, OpenTelemetry, and Helm.

Github Project Updates

Internals, APIs, and Documentation
  • Sean updated the SNMP metadata provisioning adapter to support incremental changes in addition to replacing all metadata
  • Bonnie and Emily did more work on the quick start guide
  • Benjamin Janssens worked on prepping a new ALEC release, including doc build cleanups and fixing Sonar issues
  • Morteza made some tweaks to the circleci dynamic config
  • James continued his work on notifications support in Horizon Stream
  • I fixed some docker container images relating to ping capabilities
  • Pushkar worked on notifications and outages for datachoices telemetry
  • Mark worked on the ignite detector client in Stream
  • Antonio continued his work refactoring Enlinkd's collection scheduling
  • Gerald got the ignite detector integrated into Skaffold and worked on some other operator fixes in Stream
  • Łukasz refactored some service code for spring injection in Stream
  • Jeffrey-David Kapp did more work on operator startup config for Stream
  • I did some other tuning of docker images
  • Thomas added some asset fields to the database in Stream
  • Freddy did more work on offheap storage improvements
  • Dmitri worked on updating the documentation related to partial config updates
  • Bonnie wrapped up doc changes for the cortex time-series plugin
  • Mark Frazier worked on Minion gRPC routing in Stream
  • Dustin worked on support for generics in the twin API
  • Alexander worked on a fix for accessing the poller config in the device config service
  • Jason worked on enabling github action test runs in Stream
  • I cleaned up the default changes in a jsoup dependabot update
  • Jason tuned memory consumption in the default Stream setup to be less hungry
  • Jeffrey-David Kapp added Grafana and Keycloak to the Kubernetes CRD in Stream
  • I did more work on backporting circle and docker changes to H30 and Meridian 2022
  • Dustin refactored some of the code for how filter rules are tracked
  • I fixed some issues triggered by Sonar as I prepped to make sure sonar submissions are working properly
  • DJ continued his work on OpenTelemetry integration
Web, REST, UI, and Helm
  • Chinh Le continued his work on the map in Horizon Stream
  • Chinh Le started on a device status UI for Stream
  • Mike Rose did more work on improving widgets in the Stream UI
  • Alberto wrapped up a bunch of Helm improvements
  • Chandra worked on REST APIs for event-driven discovery from traps in Stream
  • Anya worked on tests and coverage in the ALEC UI
Contributors

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

  • DJ Gregor
  • Jason Berry
  • Mark Frazier
  • Chinh Le
  • Dustin Frisch
  • Łukasz Dywicki
  • Alexander Chadfield
  • Benjamin Reed
  • Bonnie Robinson
  • Morteza Ershad-Manesh
  • Chandra Gorantla
  • Antonio Russo
  • Jesse White
  • Thomas Bigger
  • Jeffrey-David Kapp
  • Benjamin Janssens
  • Emily Marsh
  • James Hutchinson
  • Dmitri Herdt
  • Gerald Humphries
  • Anya Rybalova
  • Pushkar Suthar
  • Freddy Chu
  • Sean Torres
  • Yang Li
  • Alberto Ramos
  • Rob Ellis
  • Mike Rose

Coming Soon: JIRA Migration

We will be migrating our JIRA issue-tracker from a self-hosted version to Atlassian's cloud version.
I don't have a timeline for this yet, but expect it in the coming months.

If you currently have an account at the OpenNMS issue tracker your account should already be migrated to JIRA Cloud, but you will need to perform a password reset with the "Can't log in?" link before you can log in.

Releases and Roadmap

OpenNMS.js 2.5.0 Released

OpenNMS.js 2.5.0 contains a bunch of dependency updates including a move to core-js v3 for compatibility, as well as a few build system cleanups, fixes for querying SNMP interfaces by node ID and a query fix for 0-indexed enums.

Upcoming September Releases

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

The next OpenNMS release day is September 14th, 2022.

We currently expect updates to Horizon 30 and all supported Meridian releases.

Next Horizon: 31 (Q4 2022)

The next major Horizon release will be Horizon 31.

It will contain a number of improvements, including:

  • a refactoring of flow APIs including support for some flow hooks in the plugin API (plugin API 1.1.0+)
  • major improvements and refactoring in Enlinkd's bridge topology mapping and collection scheduling
  • more stuff, which I haven't had a chance to go back and enumerate yet, watch this space :D
Next Meridian: 2023 (Q1 2023)

Meridian 2023 is still reasonably early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.

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

Open Source Summit Europe - Dublin, Ireland - September 13th through 16th

We are a silver sponsor this year for Open Source Summit, and will be hosting a booth in the exhibition area.

Craig Gallen and some of the crew from Belfast will be there, so pop on by and say hello.

Open Source Day 2022 - September 16th

The OpenNMS Group is proud to support Grace Hopper Conference's Open Source Day (OSD) 2022, and our very own Sandy Skipper is serving on the OSD Steering Committee.

OSD is an all-day hackathon in which participants of all skill levels learn about open source while contributing to projects designed to solve real world problems.
The goal is to celebrate and encourage women in open source.

OSD will take place as a pre-event on Friday, September 16 from 8am - 3pm PDT. Participation is open to anyone who has a GHC registration ticket (in-person or virtual).

For more information, contact Sandy Skipper or see the OSD site.

Grace Hopper Celebration - Orlando, FL - September 20th through 23rd

In addition to our involvement in Open Source Day, Veena Kannan will be presenting a virtual lightning talk at the Grace Hopper Conference titled "Open Source 101 – Myth Buster Edition" at the Grace Hopper Celebration.

Her talk will be Thursday the 22nd, at 11:00am.

All Things Open - Raleigh, NC - October 30th through November 2nd, 2022

All Things Open is local to our headquarters, and is a truly fantastic event.
We love it so much, we will be the exclusive live stream sponsor. 😉

We'll also have a booth in the exhibition hall.
A bunch of OpenNMS folks will be attending and/or helping out in the booth, so please be sure to say hi!

Open Source Monitoring Conference - Nuremberg, Germany - November 14th through 16th

The OpenNMS Group is a gold sponsor of OSMC this year, and will have a booth as well.
Stop by and say hello!

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.

- Ben

Resolved Issues Since Last OOH

  • ALEC-179: Tests on Situation Detail and situation metrics
  • HELM-334: Entity Datasource does not provide node information
  • HELM-345: Alarm Details missing TroubleTicketState if state is 0
  • HS-201: Backend: New Notification Service
  • HS-203: DevOps: New Notification service
  • HS-241: Add Cucumber IT for validating minion end point
  • HS-286: Add Trapd support in Stream
  • HS-295: Integrate KeyValueStore ( PostgresJsonStore) into Horizon Stream
  • HS-296: Add Config Service
  • HS-299: Setup instructions for local-sample dir
  • HS-304: FE - Display list of devices in the geomap table
  • HS-329: Tag / Surveillance Category Membership View / Edit Panel and Add to Placeholder Device Status Page
  • HS-334: Add Grafana DB config to Devops and test default dashboard.
  • HS-335: FE - Widget component & grid layout
  • HS-336: Stats: Local Environment setup in Docker for HS Stats testing
  • HS-345: BFF: Impove the BFF performace
  • HS-346: FE - Add new device status route / container component
  • HS-347: Configure in memeory cache in BFF for backend request.
  • HS-352: Nonblock requst from BFF to platform core
  • HS-356: Propagate Skaffold --skip-tests flag into custom maven builds
  • HS-358: Use Liquibase for notification database
  • HS-360: UX competitive analysis board in Figjam on Kentik
  • HS-378: BFF migration to Webflux broke context path config
  • HS-383: Add all images we build to HS CRD
  • NMS-13864: Package description for Minion and Sentinel reference Wiki
  • NMS-14360: BmpIT flapping
  • NMS-14522: Add CAP_NET_BIND_SERVICE capability to the java binary to bind privileged ports
  • NMS-14582: Add KPI for DCB cumulative web UI entries
  • NMS-14615: Quick Start: Import inventory
  • NMS-14623: Add KPIs for open notifications and outages to datachoices telemetry
  • NMS-14624: Add KPI for application count to datachoices telemetry
  • NMS-14648: Rename OIA to OPA in git repo
  • NMS-14667: Official docs readiness for Cortex TSS plugin release
  • NMS-14728: Add Elasticsearch 7.17.6 to Drift plugin versions

The post OpenNMS On the Horizon – September 12th, 2022 appeared first on The OpenNMS Group, Inc..

by RangerRick at September 12, 2022 04:58 PM

OpenNMS.js v2.5.0

This release contains a bunch of dependency updates including a move to core-js v3 for compatibility, as well as a few build system cleanups, fixes for querying SNMP interfaces by node ID and a query fix for 0-indexed enums.

by RangerRick at September 12, 2022 02:20 PM

September 06, 2022

OpenNMS.js v2.5.0

OpenNMS.js 2.5.0 contains a bunch of dependency updates including a move
to core-js v3 for compatibility, as well as a few build system cleanups,
fixes for querying SNMP interfaces by node ID and a query fix for
0-indexed enums.

by RangerRick at September 06, 2022 08:40 PM

OpenNMS On the Horizon – September 6th, 2022

It's time once again for OpenNMS On the Horizon.

Since last time, we worked on ALEC (situation datasource, UI timeline), CircleCI config improvements, device config backup telemetry, Horizon Stream (Minion gRPC, Minion gateway, ICMP/SNMP polling, traps, PagerDuty integration, operator and Skaffold, Sonar code coverage, Spring Boot, maps, and UI), Documentation (style guide, doc-writing guide, quick start, events, DCB, Cortex time-series), offheap queueing for time-series, Docker image publishing and ARM improvements, Sonar CI fixes, publishing to Maven Central, Helm queries and flows, web UI fixes, DCB analytics, partial updates for config REST.

Github Project Updates

Internals, APIs, and Documentation
  • Benjamin Janssens added some additional fields to the ALEC situation data source.
  • Morteza worked on some tweaks to the dynamic CircleCI config.
  • Alex and Alexander added an integration test for device config backup telemetry.
  • Łukasz continued his work on Minion gRPC integration in Horizon Stream, including bringing over ICMP and SNMP RPC implementations.
  • Yang Li worked on caching for the device BFF backend in Stream.
  • Bonnie did more work on the quick start documentation.
  • Chandra incorporated the config API into Stream.
  • Pushkar added application count to the datasources telemetry.
  • Alex fixed an issue with device config node telemetry.
  • Patrick worked on some fixes for unique system IDs.
  • Mark Mahacek worked on documentation for writing documentation. ;)
  • James did more work on PagerDuty support in Stream.
  • Jason made some fixes to Stream local resource usage.
  • Mark Frazier and Gerald did more work on Skaffold for Stream.
  • Emily did more work on the style guide.
  • Arthur continued his work on the Kafka Minion gateway in Stream.
  • Gerald worked on Sonar integration in the Stream build.
  • Dustin updated some event-related documentation.
  • Freddy continued to work on enhancements to offheap time-series queueing.
  • I merged my enhancements to docker container generation and publishing, including normalizing support for ARM images.
  • Gerald worked on some Spring Boot changes in the Stream Minion gateway.
  • Chandra added trap consumption to Stream.
  • I worked on fixing up issues in running Sonar code coverage.
  • Bonnie updated some device config backup documentation in the operation guide.
  • I did some preliminary work backporting dynamic config and docker changes to earlier branches.
  • I worked on what needs to be done to publish full build Maven artifacts to Central.
  • Bonnie did some more work on Cortex time-series plugin documentation.
Web, REST, UI, and Helm
  • Chinh Le continued to work on tuning device support in the Horizon Stream map.
  • Anya worked on using the ALEC situation REST datasource in the UI.
  • Alberto did some additional work on improvements to Helm queries, including node handling and flows.
  • Christian fixed some escaping in a few web element spots.
  • Rob worked on fixing an issue with device lists.
  • Scott did more work on device config backup analytics in the UI.
  • Mike Rose worked on refactoring how widgets get wrapped in the Stream UI.
  • Dmitri merged his work on partial update support in the config REST API.
Contributors

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

  • Emily Marsh
  • Alberto Ramos
  • Patrick Schweizer
  • Benjamin Janssens
  • Chandra Gorantla
  • Benjamin Reed
  • Bonnie Robinson
  • Jason Berry
  • Chinh Le
  • Anya Rybalova
  • Yang Li
  • Alex May
  • Morteza Ershad-Manesh
  • Rob Ellis
  • James Hutchinson
  • Christian Pape
  • Pushkar Suthar
  • Łukasz Dywicki

Coming Soon: JIRA Migration

We will be migrating our JIRA issue-tracker from a self-hosted version to Atlassian's cloud version.
I don't have a timeline for this yet, but expect it in the coming months.

If you currently have an account at the OpenNMS issue tracker your account should already be migrated to JIRA Cloud, but you will need to perform a password reset with the "Can't log in?" link before you can log in.

Releases and Roadmap

Upcoming September Releases

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

The next OpenNMS release day is September 14th, 2022.

We currently expect updates to Horizon 30 and all supported Meridian releases.

Next Horizon: 31 (Q4 2022)

The next major Horizon release will be Horizon 31.

It will contain a number of improvements, including:

  • a refactoring of flow APIs including support for some flow hooks in the plugin API (plugin API 1.1.0+)
  • major improvements and refactoring in Enlinkd's bridge topology mapping and collection scheduling
Next Meridian: 2023 (Q1 2023)

Meridian 2023 is still reasonably early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.

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

Open Source Summit Europe - Dublin, Ireland - September 13th through 16th

We are a silver sponsor this year for Open Source Summit, and will be hosting a booth in the exhibition area.

Craig Gallen and some of the crew from Belfast will be there, so pop on by and say hello.

Open Source Day 2022 - September 16th

The OpenNMS Group is proud to support Grace Hopper Conference's Open Source Day (OSD) 2022, and our very own Sandy Skipper is serving on the OSD Steering Committee.

OSD is an all-day hackathon in which participants of all skill levels learn about open source while contributing to projects designed to solve real world problems.
The goal is to celebrate and encourage women in open source.

OSD will take place as a pre-event on Friday, September 16 from 8am - 3pm PDT. Participation is open to anyone who has a GHC registration ticket (in-person or virtual).

For more information, contact Sandy Skipper or see the OSD site.

Grace Hopper Celebration - Orlando, FL - September 20th through 23rd

In addition to our involvement in Open Source Day, Veena Kannan will be presenting a virtual lightning talk at the Grace Hopper Conference titled "Open Source 101 – Myth Buster Edition" at the Grace Hopper Celebration.

Her talk will be Thursday the 22nd, at 11:00am.

All Things Open - Raleigh, NC - October 30th through November 2nd, 2022

All Things Open is local to our headquarters, and is a truly fantastic event.
We love it so much, we will be the exclusive live stream sponsor. 😉

We'll also have a booth in the exhibition hall.
A bunch of OpenNMS folks will be attending and/or helping out in the booth, so please be sure to say hi!

Open Source Monitoring Conference - Nuremberg, Germany - November 14th through 16th

The OpenNMS Group is a gold sponsor of OSMC this year, and will have a booth as well.
Stop by and say hello!

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.

- Ben

Resolved Issues Since Last OOH

  • ALEC-165: Timeline alarms
  • ALEC-173: Situation endpoint with more data
  • ALEC-175: Use new situation endpoint
  • ALEC-176: Improve getSituationStatusList endpoint
  • ALEC-177: Fixes situation metrics
  • HELM-336: Flow DS query interfacesOnExporterWithFlows() does not accept FS:FID as argument
  • HELM-337: exporterNodesWithFlows() query handles criteria differently than other queries
  • HS-315: Remove unnecessary step from main README
  • HS-320: Production build of the Vue.js app
  • HS-327: Skaffold is always triggering builds of Jib-based images like notification and rest-server, even when nothing has changed
  • HS-341: java.lang.Double on adding multiple devices
  • HS-349: Skaffold file sync stopped working in UI project
  • HS-350: Trigger SonarCloud code scanning jobs in Horizon Stream
  • NMS-13553: docs.opennms.com directory listing beautification
  • NMS-14310: provisiond config partial update
  • NMS-14449: Rest API v2 for obtaining a list of SNMP interfaces doesn't return back node id
  • NMS-14542: Event / Alarms filtering no longer works
  • NMS-14555: Development and test environment for Velocloud SD-WAN integration
  • NMS-14579: Add KPI for DCB device count by sysObjectID
  • NMS-14580: Add KPI for DCB cumulative config count
  • NMS-14581: Add KPI for DCB cumulative backup failure count
  • NMS-14626: Publish images to Docker Hub
  • NMS-14655: Appliance: Minion fails to come up with 30.0.2 and bleeding image
  • NMS-14657: Graph page doesn't escape <> in resource labels
  • NMS-14669: Dynamic Yaml generation: Simplify and improve dynamic generation
  • NMS-14673: Implement VCO API v1 authentication
  • NMS-14674: Implement Velocloud API version abstracton layer
  • NMS-14687: UI update for DCB KPI
  • NMS-14688: REST API update for DCB KPI
  • NMS-14690: Need to get Sonar Cloud runs going again.
  • NMS-14691: Dynamic Yaml generation: handle merge-foundation branch and when build-trigger override file is detected better
  • NMS-14696: Upgrade dom4j to latest version
  • NMS-14697: Investigate the failure in integration-test job
  • NMS-14706: Dynamic Yaml Generation: Code Improvements to how we detect merge-foundation branch and changes to epoch file and documentation

The post OpenNMS On the Horizon – September 6th, 2022 appeared first on The OpenNMS Group, Inc..

by RangerRick at September 06, 2022 08:15 PM

August 30, 2022

OpenNMS is now a CNA!

The security team at The OpenNMS Group has partnered with MITRE to become a Common Vulnerability and Exposures (CVE) Numbering Authority (CNA). Through the CVE program, MITRE ensures that application vulnerabilities are uniquely identified and accurately reported.

As a numbering authority, The OpenNMS Group security team will assign numbers to vulnerabilities and exposures identified within our projects and products. Any vulnerability scanning tool can use CVE numbers to help users identify and manage vulnerabilities within their infrastructure. Using unique CVE identifiers, users and stakeholders across the information security community can remain informed of vulnerabilities and how to address them.

“In our continuing effort to enhance our cybersecurity program, I am excited to take this next step of becoming a CNA,” says Jeff Jancula, Chief Information Security Officer at The OpenNMS Group. “As a CNA, OpenNMS has an avenue to transparently share security information with our customers and the open source community. CVEs also let us publicly recognize community members and customers that help improve the security of our projects. These improvements will strengthen our community relationships and help reduce risk associated with vulnerabilities.”

OpenNMS is a scalable and highly configurable open-source network management platform with comprehensive fault, performance, and traffic monitoring. OpenNMS routinely promotes responsible disclosure of potential cybersecurity vulnerabilities. Read more at opennms.com/security.

The post OpenNMS is now a CNA! appeared first on The OpenNMS Group, Inc..

by Gabriela Lopez at August 30, 2022 01:31 PM

January 13, 2022

OpenNMS.js v2.4.1

This is just a rerelease to fix an issue with artifact generation in 2.4.0.

by RangerRick at January 13, 2022 02:43 PM

OpenNMS.js v2.4.0

This release includes a ton of dependency updates, as well as an enhancement to specify whether a remote OpenNMS system supports the newer, more efficient, query API for selecting resources.

by RangerRick at January 13, 2022 02:05 PM

OpenNMS.js v2.3.0

This release adds support for querying SNMP interfaces, monitored services, and outages.

by RangerRick at January 13, 2022 01:57 PM

August 23, 2021

OpenNMS.js v2.2.0

This release bumps a bunch of dependencies, plus it adds support for the api/v2/ipinterfaces API.

by RangerRick at August 23, 2021 09:03 PM

OpenNMS.js v2.1.1

This is a rerelease of 2.1.0 with a fix for documentation generation.

by RangerRick at August 23, 2021 09:03 PM

May 03, 2021

OpenNMS.js v2.1.0

This release adds support for some flow APIs coming in OpenNMS Horizon 28, as well as a documentation rework and tons of dependency updates.

by RangerRick at May 03, 2021 07:28 PM

April 13, 2020

OpenNMS.js v2.0.2

Just a small bugfix release to facilitate OpenNMS Helm fixes.

Bug Fixes

  • rest: fix response type handling in grafana 6.7 (HELM-232) (874cd80)

by RangerRick at April 13, 2020 09:17 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

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

August 05, 2019

OpenNMS.js v1.2.0

This is a small release which adds support for a default timeout in GrafanaHTTP, as well as adding X-Requested-With headers to requests (NMS-9783).

Bug Fixes

  • http: add timeout to GrafanaHTTP (22bdd70)

Features

  • rest: NMS-9783: add X-Requested-With header to requests (e803726)

by RangerRick at August 05, 2019 07:57 PM

June 07, 2019

OpenNMS.js v1.5.0

This release includes support for some additional flow queries, as well as a few security updates and a fix for CLI formatting.

Bug Fixes

  • cli: fix broken table formatting in prod cli build (JS-33) (db50724)
  • security: update handlebars, js-yaml, and marked (f5f4ad2)
  • security: upgrade to Axios 0.19.0 (a731c60)

Features

by RangerRick at June 07, 2019 09:56 PM

April 09, 2019

OpenNMS.js v1.4.0

This is a small feature release with a few changes targeted primarily to Helm.

Features

  • alarms: HZN-1492 : Add RootCause and Tags to SituationFeedback (#35) (3790072)
  • dao: JS-29 - add support for "isAcknowledged" on alarms (ff1515a)

by RangerRick at April 09, 2019 07:50 PM

March 27, 2019

OpenNMS.js v1.3.1

This is a minor release with a fix for the properties cache and a cleanup of dependencies.

Bug Fixes

  • build: JS-28 - don't mangle function names (07100ca)
  • build: JS-31 - fix all outstanding audit warnings (ace9779)
  • cli: fix alarm cli when no alarms are returned (75c6a9a)

Features

  • api: JS-30 - reconstitute Filter/Clause/Restrictions from JSON (891bbd1)

by RangerRick at March 27, 2019 05:54 PM

December 07, 2018

OpenNMS.js v1.3.0

This release contains a number of new features and a few bug fixes, including support for correlation alarms and feedback, and additional metadata for Helm 3.

Bug Fixes

  • api: support flow data (bd8c5b9)
  • feedback: Serialize the enum as a string (3c2f997)

Features

  • alarms: HELM-110: store managedObject* if present (2b86722)
  • alarms: HELM-114: alarm property for whether it is a situation (a54b627)
  • api: add flow and situation metadata APIs (42d7a58)
  • api: Add more test assertions for AlarmSummaryDTO (0f45e79)
  • api: Add test for AlarmSummary and reductionKey (3329cf7)
  • api: HZN-1357 expose FeedbackDAO (d354040)
  • api: HZN-1357 Pass data and set accept header (0bf0bdd)
  • api: HZN-1357 tests for uri.js (e98cfa4)
  • api: HZN-1357 use AlarmId for Situation (3d9f172)
  • api: Initial work (fa62503)
  • api: Move from 'impacts/causes' to 'relatedAlarms' (3bc5b6e)
  • api: OCE-REST extend Alarm and summary (e855134)
  • api: OCE-REST extend Alarm and summary (24ca0f7)
  • api: OCE-REST remove inSituation attr (d3bb9e9)
  • api: OCE-REST updte tests (abd86d1)
  • cli: improve table rendering (da92bdb)
  • feedback: Expose the feedback type enum values (500632a)

by RangerRick at December 07, 2018 04:37 PM

May 21, 2018

OpenNMS.js v1.2.2

Just a small release to fix a bug encountered in OpenNMS Helm when the new Drift ReST API returned no exporters.

Bug Fixes

  • dao: HELM-91: fix handling non-array results (0707ac7)

by RangerRick at May 21, 2018 08:37 PM

April 13, 2018

OpenNMS.js v1.2.1

Bug Fixes

  • rest: fix HTTP timeout configuration to be more consistent (c8e7162)

by RangerRick at April 13, 2018 05:36 PM

March 16, 2018

OpenNMS.js v1.1.1

1.1.0 had a build dependency that snuck into the runtime dependencies and caused a number of unnecessary projects to get pulled in. This release is identical to 1.1.0 with that dependency fixed.

by RangerRick at March 16, 2018 09:45 PM

OpenNMS.js v1.1.0

This release adds support for telemetry (Netflow) APIs which will be introduced in OpenNMS 22.x. It also includes a number of build optimizations and updates since v1.0.3.

by RangerRick at March 16, 2018 09:44 PM

February 13, 2018

OpenNMS.js v1.0.3

This is a small release with documentation updates, an API for stringifying model objects, and enabling search properties in the NodeDAO.

by RangerRick at February 13, 2018 03:37 PM

September 25, 2017

OpenNMS.js v1.0.2

This is a bugfix release to fix support for making ReSTv2 queries against OpenNMS Horizon 20.1.x.

by RangerRick at September 25, 2017 03:45 PM

September 13, 2017

OpenNMS.js v1.0.1

This is a small release to fix an authentication issue in the Grafana HTTP interface.

by RangerRick at September 13, 2017 11:54 PM

September 08, 2017

OpenNMS.js v1.0.0

This is the first official release of OpenNMS.js.

OpenNMS.js currently supports a subset of the OpenNMS ReST API:

  • query alarms, events, and nodes (including complex queries against OpenNMS Horizon 21+ and Meridian 2017+)
  • acknowledge, escalate, and clear alarms
  • create, update, and close trouble tickets against an alarm
  • create, update, and delete alarm sticky memos
  • create, update, and delete alarm journal memos

Changes since 1.0.0-beta.1

Bug Fixes
  • api: add missing modules to API export (53fad98)
  • api: add workaround for Error init + clean up docs (6f7a4ab)
  • dao: Map troubleTicketState properly (JS-24) (86fc298)
  • dao: URL-encode FIQL values (NMS-9578) (9a335e8)
  • rest: Do not reset headers when headers defined (2f360fd)
  • rest: Do not set responseType on request (0c2b6f4)
  • rest: Use err.data.response if exists as message (4875b9c)
  • rest: use negative offset for dates to work around a server issue (abdfc0b)
Features
  • alarms: expose a link to the alarm details page (HELM-55) (8795818)
  • api: add metadata call to detect ticketer config support (bf0255b)
  • api: Include ticketer configuration. JS-17 (2728734)
  • dao: Add capability to fetch values from alarm v2 endpoint (JS-22) (637443f)
  • dao: Add more complex null value handling for v2 (JS-20) (7817b4a)
  • dao: add user parameter to unack (JS-19) (90c128d)
  • dao: expose the event label and locations (HELM-13) (3395039)
  • dao: Include troubleTicketLink if defined (JS-23) (7420218)
  • dao: support dates in query parameters (JS-15) (d9884b6)
  • internal: add utility methods for dealing with dates (c40450b)
  • rest: Improve OnmsError object and GrafanaHttp error handling (72d6e32)
  • rest: only parse requests on success (JS-13) (aa9257d)

by RangerRick at September 08, 2017 07:22 PM