The OpenNMS Group, a subsidiary of NantHealth, announced OpenNMS Horizon 30, the latest major release of OpenNMS’ open source network monitoring solution.
With the Horizon 30 release, OpenNMS is now improving network traffic analysis by providing advanced NetFlow thresholding and centralized storage of network device configurations, among other enhanced capabilities ideal for the enterprise.
Alongside Horizon 30, OpenNMS also announced the official release of the OpenNMS Plugin API 1.0, which provides the developer community with a reliable resource for building plugins that exchange information between OpenNMS and other systems.
“Horizon 30 provides a rich set of significant improvements to our NetFlow capabilities, not just with performance, but also by adding fine-grained analysis of network conversations,” said David Hustace, CEO of The OpenNMS Group. “We’ve also officially released our plugin API that facilitates the development of plugins that natively integrate a customer’s network infrastructure with the platform. This 1.0 version ensures compatibility against future Horizon releases preserving customer contributions across future releases.”
With Horizon 30, OpenNMS builds on its existing support for traffic analysis by introducing the ability to generate alarms in real time by analyzing the flow data with algorithms that support high, low, and relative change threshold computations. Users can now define fine-grained monitoring of network circuits to help detect anomalies and changes in network traffic, thus ensuring circuits stay healthy, and bandwidth-related issues are identified promptly.
New to Horizon 30, users are now able to back up network device configurations on demand and/or schedule periodic backups. Horizon provides storage of centralized device configurations for comparative analysis in the event of an unexpected configuration change and the ability to manually restore backed up configurations.
Additional features and enhancements of Horizon 30 include:
- OpenNMS Grafana Plugin Update (Helm 8.0): Provides updates to the integration between OpenNMS and Grafana to deliver a combination of fault, performance, and NetFlow data visualization in a single solution. Grafana dashboards built using OpenNMS Helm can now incorporate filtering by monitoring location, offer swapping of ingress and egress flow metrics, and take advantage of wildcard support to display data more dynamically than ever before.
- Improved Device Inventory Workflow: A new way to configure the monitored device inventory subsystem, bringing both a user-friendly interface and a powerful API backend.
- OpenAPI Support: Allows users to interact with the OpenNMS REST API directly from a web browser, accelerating understanding and shortening time to value.
- Event-sourced Data Collection: Bridges fault-management and performance-management, enabling extraction of performance metrics from the fault-management domain. Metrics contained in SNMP traps or syslog messages can now be persisted for visualizing and thresholding.
- Architecture for Learning-Enabled Correlation (ALEC) Topology Provider: Users can now view correlated situations and their constituent alarms on the topology map, as well as in list form.
With the official release of the Plugin API 1.0, OpenNMS provides a development ecosystem that facilitates integration of network infrastructure into a generalized framework of events, metrics, flows, and topology. OpenNMS features many integration points, making it a solid platform on which to build the monitoring solution an organization needs. The Plugin API clearly identifies, documents, and provides ongoing compatibility guarantees for those integration points, developers can create plugins that target a clear set of interfaces and work with a broad range of OpenNMS releases. As the Plugin API adoption increases, the community will benefit from an ecosystem of plugins that can be built more quickly, validated more easily, and assured to be compatible with future releases of OpenNMS.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.