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 | Networking Monitoring Hardware |
|---|---|
| Licenses | GPL |
Recent releases
- 23 Jun 2009 08:22
Changes: This release improved the Provisiond code and added ACLs, RANCID reports, and thresholding fixes. It enables maps by default and has an entirely new way to create the OpenNMS database.
- 18 May 2009 17:16
Changes: This release only includes small feature enhancements and bugfixes.
- 06 Apr 2009 20:58
Changes: This release only includes small features and bugfixes. These include improvements to the thresholding system, a new BGP peer monitor, and visual improvements to the charting system.
- 06 Apr 2009 20:58
Changes: This release includes a large number of new features, including a replacement for capsd called provisiond, WMI support, a Layer 2 SNMP status poller, an integration with RANCID, and Asterisk notification support (send notifications through your Asterisk server). Note that you should only use 1.7.x in production with extreme caution, as it is designed as a development release until it has been fully tested.
- 16 Jan 2009 00:16
Changes: This is the first development release of what will become 1.8.0. This is an unstable release and is meant to be more of a technology preview than to be used in production. There are a number of architectural changes, including Spring 2.5 support, DAO updates, and preparation for OSGi support. A number of new features are included, such as a RESTful interface for much of the data, a replacement for capsd called provisiond, and WMI support.
- All comments
Recent commentsRe: 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.
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.
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!
Re: SQL independence.
>
> %
> % % Are there any plans for database
> % % independence?
> %
> %
> % With 2.0, the next big development
> push,
> % we are using
> % Hibernate (http://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 (http://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
Re: SQL independence.
>
> % Are there any plans for database
> % independence?
>
>
> With 2.0, the next big development push,
> we are using
> Hibernate (http://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.