Icinga is an open source network monitoring platform. It includes automation, modularized integration packages, and prebuilt alerts and reporting capabilities.
N/A
Nagios Core
Score 7.8 out of 10
N/A
Nagios provides monitoring of all mission-critical infrastructure components. Multiple APIs and community-build add-ons enable integration and monitoring with in-house and third-party applications for optimized scaling.
N/A
Splunk Enterprise
Score 8.6 out of 10
N/A
Splunk is software for searching, monitoring, and analyzing machine-generated big data, via a web-style interface. It captures, indexes and correlates real-time data in a searchable repository from which it can generate graphs, reports, alerts, dashboards and visualizations.
PRTG was the solution that was implemented before. As Icinga is Open Source we saved the licensing fee, as we ran out of free checks. I also had knowledge in Icinga so we switched over.
Nagios is inferior to Icinga in my opinion, as Icinga has the better Web UI, which I use the …
Icinga was initially a fork of Nagios. Over time, the configuration language was replaced with something more programmatic. This configuration language is one of the big sellers of this product. It allows flexible, quick configuration of large sets of hosts and services with …
While Icinga holds its own against old stalwarts like Nagios and Zabbix, it simply can't compete with the new generation of SaaS service/server monitoring software in terms of ease of use, feature-completeness, integration with things like Cloudwatch, CloudHealth, New Relic, …
There are two main competitors of Icinga in my opinion, Nagios, and NetFlow based monitoring solutions. Both are good, Icinga, is a more refined version of Nagios with a much better API and backwards compatibility to the platform. If you are running Nagios, you can transfer …
Icinga is better than Nagios because of its nicer user interface. New Relic can monitor CPU/memory and disk usage, but it's more of a performance and application troubleshooting tool rather than monitoring.
Nagios may not have as much metrics reporting or as many visualizations as the other products, but outdoes the others in ease of configuration and the ability to deliver multi-faceted alerting across a variety of applications, with the help of plugins or with the user …
We selected Nagios because of the size of its community. We've used some of the others in the field over the past few years, Nagios had the best features out of the box coupled with it's following made it an easy selection.
Nagios is a good start, but as soon as an alert is triggered, you have to go searching and digging. It's better as a trigger and integrated with more robust, intelligent monitoring tools.
Nagios is an easy to use intuative tool that gives a great return on investment. It has better monitoring features that IT needs than competitors and won't break the bank. Support for this tool is first class and the techs will help you to get the most out of the product.
Icinga is a world-class monitoring system. It can be used for most general monitoring situations. It is not a silver bullet, however, and there are instances where domain-specific monitoring systems are necessary. However, the output from those monitoring systems can be funneled into Icinga as a central monitoring and alerting system.
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.
I'm liking the newer products, and I'm looking forward to how they integrate with the overall product when they come together. Just log in and be able to query a large number of systems for similar issues or a unique one. That is a great fit for Splunk Enterprise, looking for a simple case or a simple String or something of that nature across multiple machines. It's a great fit for that to identify issues or particular software, whatever your scenario is, String, to find it across any particular server or group of servers, so that you can update or do a deployment or whatever it is you're looking to do.
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.
Icinga is a solid solution which does everything it promises. It is backwards compatible with most Nagios instances, making the transition very easy. Once you get the hang of installing new plugins and editing configuration files expanding its monitoring capabilities are easy.
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.
We are using Splunk extensively in our projects and we have recently upgraded to Splunk version 6.0 which is quite efficient and giving expected results. We keep track of updates and new features Splunk introduces periodically and try to introduce those features in our day to day activities for improvement in our reporting system and other tasks.
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.
You can literally throw in a single word into Splunk and it will pull back all instances of that word across all of your logs for the time span you select (provided you have permission to see that data). We have several users who have taken a few of the free courses from Splunk that are able to pull data out of it everyday with little help at all.
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.
Splunk maintains a well resourced support system that has been consistent since we purchased the product. They help out in a timely manner and provide expert level information as needed. We typically open cases online and communicate when possible via e-mail and are able to resolve most issues with that method.
The online course was simple clear and described the main capabilities of the solution. There is also an initial module that can be done for free so anyone can familiarize themselves with the functionality of this solution. On the other hand, however, there could be more free online courses. Maybe even with a certificate, this would broaden the group of people who are familiar with the platform while increasing familiarity with the solution itself.
Icinga is better than Nagios because of its nicer user interface. New Relic can monitor CPU/memory and disk usage, but it's more of a performance and application troubleshooting tool rather than monitoring
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].
A lot of products have natively inside their own dashboards and or their own logging repositories. And each one is difficult to learn or they're too complex or they're not verbose in the sense that they're not easy to mine the data that you're looking for. So that could be anything from the native logging that you find in other Cisco products. It's easier to use Splunk to draw the data that you're looking for as opposed to going to the individual's products themselves to get the logs that you're looking for.
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.
Splunk has allowed developers to diagnose production issues when access of control was taken away from them to be allowed to view items in production environments and I believe that is invaluable.
At times some developers weren't super happy about using it, but it was more of the fact that they were used to having production access and not creating their splunk queries to get information.
Going one place to view logs was very beneficial to have.
