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
- 08 Apr 2013 22:24
Release Notes: This release contains a number of bugfixes and small feature enhancements, most notably a fix for remote poller startup issues when certain plugins are enabled, a CIFS monitor, an optional change to the front-page outage list, and many other tweaks. It is a recommended upgrade for all users.
- 05 Apr 2013 22:28
Release Notes: This is the first release candidate for what will become the 1.12 stable series. It includes a large number of changes including architectural updates (Spring 3, OSGi, and more), a number of new mapping features, trouble ticket integration with JIRA and Remedy, and much more.
- 24 Jan 2013 13:55
Release Notes: This stable release contains a number of bugfixes, including fixes for a number of collectors and detectors, and support for the latest PostgreSQL release. It is a recommended upgrade for all users.
- 20 Nov 2012 00:24
Release Notes: 1.10.7 is the latest in the stable series of OpenNMS. It contains a number of small bugfixes, including graphing fixes, a fix for thresholding on data collection which retrieves multiple values (like StrafePing), and a few other things. It also adds support for adding user documentation/annotations on alarms.
- 12 Oct 2012 19:41
Release Notes: This release is in the unstable series, which will become the stable 1.12.x series. It includes a number of bugfixes and enhancements, including support for the CIDR route table for populating Linkd information.
Recent comments
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.
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 (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
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.
Heartbeat
- Popularity Score
- 1,070.98
- Vitality Score
- 107.85
- Subscriptions
- 249
