Nagios Core Reviews

The poller is really good, I can easily implement new stuff and it is scalable.

Monitoring is the most important thing to avoid any production issue. It's important to get some alerts on the server and network devices. It's the day-to-day management to avoid any production issues.

I have used Nagios with the Adagios interface for two years.

I have not yet encountered any issues with deployment, stability or scalability.

I used Centreon/Nagios for eight years before I chose Nagios with the Adagios interface to simplify day-to-day configuration.

Implementation requires knowledge on the production.

There is no license cost, just a cost in time.

There is a large Nagios community for new sensors, etc.

We started experimenting with Nagios six years ago to get a feel of it as a recommended network monitoring system. We tested other products like opennms, zabbix and zenoss but we finally decided to go for Nagios as it was very extensible. At that time, only Nagios could be configured to work with our in-house developed SMS-based messaging system. This is probably the greatest advantage of Nagios - it can be customized to a degree to suit your monitoring needs. It's architecture also allows distributed monitoring, which is really a great feature to reduce network traffic.

Nagios' great customizability is also one of it's greatest drawback. In the early days, installation and configuration of nagios was not for the faint of heart. You need a lot patience and system administration skill to figure out what gets into what file. This is still true today, as some still install nagios from source. Aside from installation, configuring nagios from the command line is very tedious, time consuming and prone to user errors. The core nagios installation from source does not provide an integrated management system for nagios, and you have to install these systems separately from nagios.Nagios is a great product. I would highly recommend this to organizations which requires a great deal of flexibility in terms of customizing their network monitoring system.

Though the core nagios system is still very challenging to install, a lot of bundled installers with very good GUI's for configuring nagios now exists. Instead of doing everything manually from the command line, you can just grab one of these packaged forks and get started with nagios in as little as 10 minutes.

The most valuable features are the reports and the way it generates the report in a graphical manner. The creating availability, the ratios, the uptime, downtime, and the outages.

Most of the issues have been covered through Nagios XI, but they could select some of the small features that are in the paid version and include them as part of Nagios Core.

Especially the graphical user interface in terms of configuration when you add in hosts, you have to use CAC and CLI to add hosts. You could use the GUI to add hosts instead.

The scalability needs improvement, it's not scalable at this time.

I have been working with Nagios Core for a couple of years.

We are using the latest version.

Nagios Core is a stable solution.

This solution is not scalable at all. If you want to add an AI, or if you wanted to monitor different types of metrics, you won't get the most out of it.

It's not scalable, which is important these days when you want to see more data and how your network is performing.

We have not contacted technical support. Most of the online documentation is helpful.

The initial setup is pretty straightforward.

I can't say how long it took to deploy as we had several deployments at the same time, but it was not a problem at all. We didn't have any issues.

We are using the open-source, unpaid version.

I would recommend it for small network deployments or if you have other open source applications or other metrics like utilization, CPU. So if you're running alongside other open source applications and in the small space, it works. But anything beyond that is not recommended.

I would rate Nagios Core a six out of ten.

On-premises

We like the automatic alerting functions. Also, there are a lot of free monitoring modules available for any purpose you may need.

We've got a medium size distributed system with a lot of locally installed machines, and Nagios provides us with a solid and reliable monitoring solution for these machines.

They should simplify the features so it becomes easier to setup out of the box.

I've been using it for about five years.

There have been no performance issues.

It's been able to scale for our needs.

Nagios was our first solution. At the time, we read that Nagios was the industry standard solution, so we chose it.

It is a complex software with many-many features, so the setup not an easy task.

We did it in-house.

We are using the free version.

The free version is good enough for most people, but it is somewhat hard to make it a working solution.

• Reliability
• Security
• Flexibility
• Functionality
• Availability - controllability anywhere and with different methods

When compared to earlier versions, it looks like 4.x has lost the statusmap.cgi module.

Update April 2016:

I have fixed the problem with statusmap.cgi by upgrading to version 4.1.1. In the old version this module had not been compiled.

I've used it for six years.

I have had no problems deploying it.

I have no stability issues.

I currently do not need to scale on my network.

Customer Service:

I only have the free version, which does not have customer service.

Technical Support:

I only have the free version, which does not have technical support.

We use Cisco ASA and MySQL devices alongside Nagios as our network infrastructure needs expanding and required more serious hardware solutions.

I believe it is hard to calculate for hardware.

I only use the free version.

• Amanda
• Cacti
• Zabbix
• Icinga (after installation).

As a rule, any device upon delivery is obsolete. Pick up the solution for your business, based on your specific needs.

Open source and very flexible. large ecosystem of tools and custom monitors built up around nagios. All configuration is text files, so it is easy to keep this in version control and generate new configs from other tools.

Default interface is clunky and slow. Can be a steep learning curve if you haven't worked with it before. Adding devices or services requires reloading the config or restarting the service. Would like for this to be more dynamic. It seems that most of the new development is going towards Nagios XI(paid enterprise version) rather than the opensource nagios. Would like to see some of the newer ideas in Icinga and/or MK livestaus integrated into opensource nagios.