Likelihood to Recommend It's a decent system if you're a pure IT shop and want to become ITIL-aligned. It forces everyone into an ITIL mentality - service level agreements, change management, and asset tracking. It's very rote, for better and for worse. It's not appropriate at all as a customer-facing or non-IT facing self-service tool. You will never get your end users to really understand how to use the interface.
Read full review Nagios monitoring is well suited for any mission critical application that requires per/second (or minute) monitoring. This would probably include even a shuttle launch. As Nagios was built around Linux, most (85%) plugins are Linux based, therefore its more suitable for a Linux environment.
As Nagios (and dependent components) requires complex configurations & compilations, an experienced Linux engineer would be needed to install all relevant components.
Any company that has hundreds (or thousands) of servers & services to monitor would require a stable monitoring solution like Nagios. I have seen Nagios used in extremely mediocre ways, but the core power lies when its fully configured with all remaining open-source components (i.e. MySQL, Grafana, NRDP etc). Nagios in the hands of an experienced Linux engineer can transform the organizations monitoring by taking preventative measures before a disaster strikes.
Read full review Pros ITIL ticketing (incidents, problems, etc.). Change orders. Matching up its asset management system with incidents/change orders. Read full review Monitoring of services is one of the biggest benefits for our company. Being able to respond in a timely fashion keeps business smooth. Hardware and device monitoring are easy to set up with proper parameters. Notification to key staff to be able to respond quickly makes issues go away faster. Read full review Cons The user interface (UX) is antiquated and clunky. Compared to ServiceNow, it feels like it's 15 years behind. It's complicated - We do routine internal training just to get people to use it correctly. It doesn't have an automated way of discovering assets. Everything has to be force-fed. Read full review Nagios could use core improvements in HA, though, Nagios itself recommends monitoring itself with just another Nagios installation, which has worked fine for us. Given its stability, and this work-around, a minor need. Nagios could also use improvements, feature wise, to the web gui. There is a lot in Nagios XI which I felt were almost excluded intentionally from the core project. Given the core functionality, a minor need. We have moved admin facing alerts to appear as though they originate from a different service to make interacting with alerts more practical. Read full review Likelihood to Renew We're currently looking to combine a bunch of our network montioring solutions into a single platform. Running multiple unique solutions for monitoring, data collection, compliance reporting etc has become a lot to manage.
Read full review Usability The Nagios UI is in need of a complete overhaul. Nice graphics and trendy fonts are easy on the eyes, but the menu system is dated, the lack of built in graphing support is confusing, and the learning curve for a new user is too steep.
Read full review Support Rating We have to hire 2 full-time 3rd-party consultants to run this application. That tells me it's not a very IT-friendly, vendor-supported application. Compare that with, say, SolarWinds, which is much easier for regular IT staff to customize without sacrificing features and capability. Sure, we have to bring in Loop1 to consult for us when we need to do a major SolarWinds config change or need a really unusual custom query built, but we never need more than 10 hours of consulting per month.
Read full review I haven't had to use support very often, but when I have, it has been effective in helping to accomplish our goals. Since Nagios has been very popular for a long time, there is also a very large user base from which to learn from and help you get your questions answered.
Read full review Alternatives Considered I did not select CA. If it were up to me, I would migrate us to
ServiceNow . The user interface on
ServiceNow is 100% more modern and 200% more user friendly. With
ServiceNow , the front page for end users makes it clear: one button that says "Ask for something" and one button that says "Report a problem". That's what our end users need. The biggest problem we have in our organization is that our end users don't report issues to the Help Desk often enough and rarely ask for things through the Help Desk. A clean, simple self-service option like this would open up a world of new information for our customer service team.
Read full review Because we get all we required in Nagios [Core] and for
npm , we have to do lots of configuration as it is not as easy as Comair to Nagios [Core]. On
npm UI, there is lots of data, so we are not able to track exact data for analysis, which is why we use Nagios [Core].
Read full review Return on Investment It helped make us an ITIL shop. It was integral during our large IT consolidation 10 years ago in merging 10 different IT departments into one by converging on one ticketing system for all IT issues. Its lack of user-friendliness has gated us from being able to deploy a true self-service IT help desk. Read full review With it being a free tool, there is no cost associated with it, so it's very valuable to an organization to get something that is so great and widely used for free. You can set up as many alerts as you want without incurring any fees. Read full review ScreenShots