OpenNMS Meridian – Enterprise Network Management Platform

OpenNMS Meridian 2025 offers comprehensive network, server, and application monitoring with modern UI redesign and enterprise-grade scalability.

About OpenNMS Meridian

OpenNMS Meridian is an enterprise-grade, open-source network management platform that delivers comprehensive fault, performance, and traffic monitoring across heterogeneous infrastructure. Licensed under AGPLv3, Meridian represents the optimized, stable release branch of OpenNMS, curated by The OpenNMS Group for production environments. The platform excels at multi-vendor device monitoring, event correlation, and custom workflow integration through its extensible architecture. Meridian 2025 introduces the most significant UI overhaul in product history, transitioning to a horizontal navigation model that reduces clicks and improves IT operator efficiency. With support for Elasticsearch 8.x, ServiceNow integration, virtual appliance deployment, and distributed Minion collectors, Meridian scales from small networks to complex enterprise environments managing tens of thousands of network elements.

System Requirements

  • Operating System: RHEL 8/9, CentOS Stream 9, Debian 9-11, Ubuntu 20.04 LTS+
  • Processor: 4 vCPU minimum, 8+ vCPU recommended
  • RAM: 8 GB
  • Disk Space: 20 GB SSD recommended
  • Additional Requirements: OpenJDK 17, PostgreSQL 13+, Elasticsearch 8.x (for flows), Cassandra 4.17.0 (optional), Docker for containerized deployment

Features Of OpenNMS Meridian

  • SNMP data collection from network devices and servers
  • Event processing and correlation with threshold-based alerting
  • Distributed monitoring using Minion remote collectors
  • Flow data processing with NetFlow v5/v9 and IPFix support
  • ServiceNow integration for event ticketing and CMDB synchronization
  • Elasticsearch 8.x support with composable index templates
  • Comprehensive reporting and SLA tracking
  • Role-based access control with multi-user management
  • REST API for external integrations and automation
  • Kafka-based event streaming for real-time processing
  • Virtual appliance deployment option for rapid evaluation
  • IPFix vendor-specific information element support
  • Kubernetes and Docker orchestration support
  • High availability with distributed components

Pros & Cons

Pros

  • Comprehensive multi-vendor network monitoring in single platform
  • Fully open-source with no licensing restrictions or per-device costs
  • Highly customizable and extensible through Plugin API framework
  • Powerful event correlation and automated alerting capabilities
  • Excellent for large-scale distributed network environments
  • Robust community support and professional services available

Cons

  • Steep learning curve requiring SNMP and event configuration expertise
  • Web UI complexity demands technical expertise; configuration requires XML knowledge
  • Large installation footprint requiring dedicated infrastructure resources
  • UI redesign in 2025 may require adaptation for existing users
  • Limited out-of-box support for cloud-native monitoring compared to pure SaaS solutions

Changelog

Version 2025.0.1 (December 2025):
- Bug fixes and enhancements across all supported branches
- Improved UI responsiveness and navigation workflows
Version 2025.0.0 (November 2025):
- Complete UI redesign transitioning to horizontal navigation
- Elasticsearch 8.x support with composable index templates
- ServiceNow plugin for event and CMDB integration
- Virtual appliance OVA image for rapid deployment
- Enhanced PKCS12 keystore support in credentials vault
- Extended metadata annotation support across entities
- IPFix vendor-specific information element support
- Deprecation of JRobin time-series storage, RRDTool default
- Java 17 requirement, PostgreSQL 13+ requirement

Frequently Asked Questions

What is the difference between OpenNMS Horizon and Meridian?

Horizon is the free, community-driven version receiving frequent updates with latest features. Meridian is the optimized, stable production release curated by The OpenNMS Group, available through subscription with SLA support, longer release cycles, and production-grade stability. Both are fully open-source under AGPLv3.

Can I run OpenNMS Meridian without commercial support?

Yes, Meridian is fully open-source under AGPLv3 and can be deployed and maintained independently. Community support is available through forums and GitHub. Commercial support subscriptions from The OpenNMS Group provide SLA guarantees, bug fixes, and strategic guidance.

How does Meridian handle large-scale network monitoring?

Meridian uses distributed Minion collectors deployed at network edges to distribute polling load and reduce latency. Elasticsearch handles flow data processing, Cassandra stores time-series data, and Kafka enables real-time event streaming across multiple instances for horizontal scalability.

Is Meridian suitable for MSP environments?

Yes, Meridian supports multi-tenant capabilities enabling MSPs to manage customer networks separately. The ServiceNow integration enables seamless ticketing workflows, and distributed collectors support monitoring geographically dispersed customer sites.

What are system requirements for production Meridian deployment?

Production deployments require RHEL 8/9 or equivalent, OpenJDK 17, PostgreSQL 13+, 8GB+ RAM (16GB+ recommended), 20GB+ SSD storage, and Elasticsearch 8.x for flow processing. Distributed deployments use Minion collectors (1-4GB RAM each) deployed across network sites.

How do I migrate from Horizon to Meridian?

Meridian is a separate, parallel release branch. Migration involves backing up your Horizon database, performing a clean Meridian installation, and restoring the database backup. The OpenNMS documentation provides detailed migration procedures and compatibility information.