Return to navigation
Read all reviews
We use OpenNMS to monitor all aspects of our networks, identify issues and to alert us of any problems. The level of detail is great, and …
[OpenNMS] is our central NMS for all networking gear, routers and switches. It supports our network operations to maintain services to our …
We're using OpenNMS to monitor our network gear across the globe. It allows our NOC to see problems quickly and engaged the proper teams …
Return to navigation
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
2 people want pricing too
Return to navigation
- Tech Details
Return to navigation
Cisco Prime LAN Management Solution
Progress WhatsUp Gold
SolarWinds Engineer's Toolset
Cisco Nexus Dashboard
Micro Focus Network Node Manager i
Companies can't remove reviews or game the system. Here's why
We use OpenNMS to monitor all aspects of our networks, identify issues and to alert us of any problems. The level of detail is great, and we can often spot and deal with potential issues before they actually manifest as a problem. When we do find ourselves with a network critical issue, OpenNMS alerts us within seconds and tells us where to look. Once you have everything running, you will wonder why you didn't do it sooner.
- Can monitor practically anything. Service availability, performance, latency, network interfaces, routing, hardware, and so on, and via different methods. If you need to monitor something on your network, you almost certainly can with OpenNMS.
- The OpenNMS web-based dashboard is very comprehensive and offers a ton of detail, covering everything you are monitoring. The ability to get a reassuring overview of the entire network is great, and to be able to whittle down the data to specifics, is a game changer.
- OpenNMS has a great online community, with a massive amount of support available via countless forums, blogs, YouTube, etc. If you get stuck on an issue, you'll find someone who's been there, done that, and detailed a resolution.
- Available free and open-source (with paid support and plans available for those who require it).
- It takes a fair amount of experimentation to fine tune information collection.
- Configuration can be quite cumbersome with a steep learning curve. It would be nice if more of this could be done via the web dashboard.
- The reliance on Java will put some users off. However, in fairness, it does mean it runs on a wide variety of hardware.
I would recommend all system administrators use some form of network monitoring if they are not already doing so, and I'd definitely recommend people consider OpenNMS if they're shopping around. Small businesses will benefit from the low-cost of entry (it's free!), whilst getting all the enterprise features. Larger businesses can benefit from paid support plans.
However, there's no getting around the fact that you will require some advanced networking and sysadmin knowledge to get the most out of OpenNMS, or at least, be prepared for a steep learning curve. If you don't have the resources to devote this time initially, you may struggle.
- Free and open-source.
- Ability to monitor practically any device or service on our networks.
- Comprehensive web based dashboard provides a wealth of information and ongoing 'health' check.
- Initial adoption required quite a lot of resources and time to get everything right. Totally worth it for us; just be prepared for a gradual process that will get better and better with time.
- Once setup and running smoothly, it provides us with all the reporting we could hope for, at near zero cost.
- With OpenNMS, we're able to offer a much more reliable service to our customers, and spend a lot less time dealing with issues.
Although Grafana is in no way an alternative to OpenNMS's full functionality, it can be integrated with other solutions (including OpenNMS itself) to offer the graphing and data visualisation aspects of OpenNMS. In this regard, Grafana is more flexible, and some would say prettier, than OpenNMS's graphing. For the best of both worlds, I'd recommend using them both!
[OpenNMS] is our central NMS for all networking gear, routers and switches. It supports our network operations to maintain services to our customers. Additionally, the system provides reporting capabilities for our customer SLAs. We also use it to help slice our network into different segments to help us track and identify areas of service issues.
- Report on SLA
- Group network areas
- Discovery of elements
- The MIB management is weak and MIB compiler
- Needs more online configuration and less by command line
- More performance troubleshooting
Large network environments with few types of devices. The system is great but getting all of the MIBs loaded and to try and create unique rules /alarm type. Alarm correlation is doable but it takes too much manual work and XML configuration. I do enjoy the dashboard and surveillance categories.
- It is not costly out of the box
- It works on many platforms.
- It is easy to use with the right hardware
With the cost of OpenNMS, it is totally worth it. Additionally, the system works on most platforms which is great. The system can be configured following how to guides and Google searches and is open so it doesn’t require specialized admins. I prefer this system and it’s extensibility. I wish more systems were as useful.
We're using OpenNMS to monitor our network gear across the globe. It allows our NOC to see problems quickly and engaged the proper teams within our large organization quickly when there are issues. As a result of implementing OpenNMS we've been able to improve response times and improve our customers' experience.
- Collecting information from various vendors and platforms.
- Displaying the information that's collected in an easily readable format.
- Notifying us of problems as soon as they arrive so that we can address them as quickly as possible.
- We've had a few issues with delayed alerting.
- I haven't quite figured out how to make topologies work yet, but I haven't spent a ton of time on it either.
- We've also had a bit of trouble importing some MIBs, but that usually boiled down to working with the vendor to make sure we had the right MIBs and dependencies.
We've been using OpenNMS for network monitoring and have been fairly happy with it. There can be a bit of a learning curve to the setup and installation which might turn some people off, but if you can work through the learning curve it's a pretty powerful tool at the awesome price of free (paid support is available).
- We've been able to improve our customers' experience.
- Because we're able to respond to issues quicker, we're able to better meet our SLAs.
- We are able to see smaller problems and address them before they become big problems.
I've setup and administered Zabbix at past jobs and now just use OpenNMS from an end user perspective while working as a Sr. Network Engineer. I think both are great products, both have steep learning curves when it comes to initial setup and installation. From the end user perspective I personally prefer Zabbix (but that's probably because I've had more time with Zabbix and learned it first,) but both provide the necessary information to improve your network monitoring.
At Federal Mogul, we used OpenNMS as an alternative to Nagios. We used it to do snmp monitoring across several platforms, including AIX, Red Hat and HP servers. This tool was also good for monitoring system uptimes, CPU and memory utilization and also Tomcat availability and Java memory and heap dumps.
- When we used OpenNMS you could download the base package for free and configure it fairly easily for your own environment. You can't beat that kind of price break.
- OpenNMS had a very nice looking GUI that was easily navigated and fairly straightforward to understand and configure.
- There were a wide variety of add-ons available for download and implementation.
- Perhaps it was our new configuration, but OpenNMS seemed to produce a lot of network traffic. This could cause problems on networks with limited bandwidth.
- During the discovery phase of implementation, it is very easy to get overwhelmed with the amount servers discovered in the environment. It might be better to limit the breadth of the discovery when beginning.
- Paid support was difficult to justify to management on a product that we downloaded and implemented for free.
For the initial cost, OpenNMS is difficult to beat and the quality of the GUI is a big plus when presenting the product to management types. In a start up position or a smaller company OpenNMS could be a very valuable asset to monitor systems and maintain availability. In larger businesses where funds may be more readily available, there are products that are more easily configurable and prettier to look at--at a cost.
- Since we implemented OpenNMS for free, the ROI was probably considered very high as it was simply the cost of my time and the installation was successful.
- If this was the only package we were using to monitor system basics, this would have been a very adequate program and would have done the job "out of the box" with very minimal configurations, but an administrator with prior SNMP and MIB installation experience could cut our installation times down and greatly increase the impact that OpenNMS could have on an environment.
- OpenNMS also had a very nice reporting tool that could produce good looking uptime, availability and usage reports for clients.
OpenNMS's more attractive GUI and its price break were the main reasons our company chose to explore and use this product. However, it never managed to actually replace Nagios which had a much more established hold within the company. Perhaps we were over-monitoring, but our company claimed a $100k loss per hour of downtime.