Projects / OpenNMS

OpenNMS

OpenNMS is the first enterprise-grade network management platform developed using the open source model. The three main functional areas of OpenNMS are service polling, which monitors services on the network and reports on their "service level"; data collection from the remote systems via SNMP in order to measure the performance of the network; and a system for event management and notifications.

Tags
Licenses

RSS Recent releases

  •  21 Feb 2014 03:52

Release Notes: This release fixes a number of bugs, including a collection error when using storeByForeignSource.

  •  13 Feb 2014 21:08

    Release Notes: This is primarily a bugfix release, containing fixes for fonts in graphing when using JRobin, more fixes for upgrades from 1.10.x, and a number of other smaller fixes, as well as new or updated support for Konica, TrendMicro, BigIron, Poseidon, and NetScaler devices.

    •  14 Dec 2013 07:39

    Release Notes: This unstable release contains a lot of changes under the covers, and a number of bugfixes and enhancements that were too invasive to include in the 1.12 series, including a major update to the topology GUI.

    •  14 Dec 2013 07:39

    Release Notes: This release fixed a bug in the upgrade process.

    Release Notes: This release contains a large number of bugfixes as well as a few enhancements, including JMX collection fixes, VMware import fixes, many thresholding improvements, and an upgrade tool to fix an incompatibility with upgrades from OpenNMS 1.10.x.

    RSS Recent comments

    14 Sep 2007 14:43 gregcopeland

    Re: SQL independence.

    > OK; it seems somewhat overkill to use

    > stored procedures for something like

    > this, and it comes with the penalty of

    > portability.

    >

    > I guess we'll just have to wait or use

    > something else, such is life in the

    > world of OS.

    It's pretty obvious you don't understand databases. OpenNMS is targeting an Enterprise Solution. Part of that need is performance. Real databases support stored procedures because they can significantly save on both CPU and disk bandwidth. Use of stored procedures also ensures a consistent API is exposed to would-be developers.

    Since you're mandating a request of MySQL plus insisting the use of stored procedures should be abandoned, you should really be looking at alternate solutions since your mandates are wholly incompatible with an Enterprise quality solution.

    14 Sep 2007 14:37 gregcopeland

    Re: SQL independence.

    > Being able to use MySQL is essential to

    > us.

    >

    >

    >

    That's pretty funny. This is like saying we can't can't buy a car until it explodes when you can least afford it. Only after it constantly explodes will you consider buying the vehicle.

    Hehehe...too funny. Shesh...just about any DB is going to prove more reliable and robust than MySQL. There is a reason why real DBAs consider MySQL to be trash...because it is. It lacks features, teaches poor SQL coding habits, isn't reliable, scales like crap, so on and so on. Seriously...if you consider MySQL to be a mandatory feature then you absolutely are not looking for an Enterprise Solution. Period.

    03 Jul 2005 23:53 joho

    Re: SQL independence.

    > Unknown at the moment. We are getting

    > ready to release 1.3.0 [..]

    >

    > We use some stored procedures that MySQL

    > did not support prior to 5, which is one

    > of the reasons the movement to MySQL

    > would be difficult.

    OK; it seems somewhat overkill to use stored procedures for something like this, and it comes with the penalty of portability.

    I guess we'll just have to wait or use something else, such is life in the world of OS.

    Thanks!

    02 Jul 2005 08:26 tarusb

    Re: SQL independence.

    >

    > %

    > % % Are there any plans for database

    > % % independence?

    > %

    > %

    > % With 2.0, the next big development

    > push,

    > % we are using

    > % Hibernate (www.hibernate.org)

    > to

    > % abstract the

    > % database layer, so it might be

    > possible

    > % to use mySQL then.

    >

    >

    > What's the plan for 2.0.. release date..

    > roadmap.. ?

    >

    > Being able to use MySQL is essential to

    > us.

    >

    >

    >

    Unknown at the moment. We are getting ready to release 1.3.0 (before LinuxWorld Expo in August) which adds SNMPv3 support, alarms and JMX monitoring.

    We use some stored procedures that MySQL did not support prior to 5, which is one of the reasons the movement to MySQL would be difficult. The OpenNMS Group (www.opennms.com) provides commercial support and services for OpenNMS, and they might be able to spec a project for you to support MySQL if the need is immediate.

    -T

    30 Jun 2005 07:12 joho

    Re: SQL independence.

    >

    > % Are there any plans for database

    > % independence?

    >

    >

    > With 2.0, the next big development push,

    > we are using

    > Hibernate (www.hibernate.org) to

    > abstract the

    > database layer, so it might be possible

    > to use mySQL then.

    What's the plan for 2.0.. release date.. roadmap.. ?

    Being able to use MySQL is essential to us.

    Screenshot

    Project Spotlight

    Infovore

    A map/reduce framework for processing large RDF data sets.

    Screenshot

    Project Spotlight

    John The Sorcerer

    An adventure game based on the Simon the Sorcerer series.