Community hub
Recent from talks
Knowledge base stats:
Talk channels stats:
Members stats:
OpenNMS
OpenNMS is a free and open-source network monitoring and network management platform written in Java. It provides fault management, performance data collection, service monitoring, event processing, and topology mapping. The project was started in July 1999 and registered on SourceForge as project 4141 in March 2000, making it one of the oldest open-source network management platforms.
OpenNMS is released under the AGPLv3. The OpenNMS Group provides commercial support, training, and an enterprise distribution called Meridian. The project itself is governed by The Order of the Green Polo (OGP), a community organization separate from the commercial entity.
Steve Giles, Brian Weaver, and Luke Rindfuss started the OpenNMS project in July 1999 at their company PlatformWorks. The project was registered on SourceForge in March 2000, about two months after the registration of NetSaint (later Nagios).
On September 28, 2000, PlatformWorks was acquired by Atipa, a Kansas City-based Linux systems vendor. In July 2001, Atipa renamed itself Oculan.
In September 2002, Oculan stopped supporting OpenNMS. Tarus Balog, then an Oculan employee, left the company to continue the project independently. In September 2004, Balog, Matt Brozowski, and David Hustace founded The OpenNMS Group to provide commercial services. The Order of the Green Polo was established shortly afterward to manage the project's governance separately from the commercial business.
OpenNMS produces two release streams: Horizon (community releases with new features) and Meridian (enterprise-oriented releases with longer support cycles).
OpenNMS is built around a publish-subscribe event bus. Internal processes and external sources (SNMP traps, syslog messages, TL/1 events, or XML messages sent to a TCP listener) generate events that other subsystems can consume. Events can trigger alarms, which support event reduction (consolidating repeated identical events into a single alarm with a counter) and correlation workflows (automatically clearing a "down" alarm when a matching "up" alarm arrives).
The alarm subsystem can integrate with trouble-ticketing systems including Request Tracker, OTRS, and Jira. An event translator can augment incoming events with additional data before forwarding them. Notifications can be sent via email, SMS, XMPP, and custom notification methods.
Hub AI
OpenNMS AI simulator
(@OpenNMS_simulator)
OpenNMS
OpenNMS is a free and open-source network monitoring and network management platform written in Java. It provides fault management, performance data collection, service monitoring, event processing, and topology mapping. The project was started in July 1999 and registered on SourceForge as project 4141 in March 2000, making it one of the oldest open-source network management platforms.
OpenNMS is released under the AGPLv3. The OpenNMS Group provides commercial support, training, and an enterprise distribution called Meridian. The project itself is governed by The Order of the Green Polo (OGP), a community organization separate from the commercial entity.
Steve Giles, Brian Weaver, and Luke Rindfuss started the OpenNMS project in July 1999 at their company PlatformWorks. The project was registered on SourceForge in March 2000, about two months after the registration of NetSaint (later Nagios).
On September 28, 2000, PlatformWorks was acquired by Atipa, a Kansas City-based Linux systems vendor. In July 2001, Atipa renamed itself Oculan.
In September 2002, Oculan stopped supporting OpenNMS. Tarus Balog, then an Oculan employee, left the company to continue the project independently. In September 2004, Balog, Matt Brozowski, and David Hustace founded The OpenNMS Group to provide commercial services. The Order of the Green Polo was established shortly afterward to manage the project's governance separately from the commercial business.
OpenNMS produces two release streams: Horizon (community releases with new features) and Meridian (enterprise-oriented releases with longer support cycles).
OpenNMS is built around a publish-subscribe event bus. Internal processes and external sources (SNMP traps, syslog messages, TL/1 events, or XML messages sent to a TCP listener) generate events that other subsystems can consume. Events can trigger alarms, which support event reduction (consolidating repeated identical events into a single alarm with a counter) and correlation workflows (automatically clearing a "down" alarm when a matching "up" alarm arrives).
The alarm subsystem can integrate with trouble-ticketing systems including Request Tracker, OTRS, and Jira. An event translator can augment incoming events with additional data before forwarding them. Notifications can be sent via email, SMS, XMPP, and custom notification methods.