What is our primary use case?
The main objective to use Nagios Core 4.x is to save significant costs on Infrastructure Monitoring without compromising the monitoring parameters.
So, deploying Nagios Core 4.x was the only option for me considering the below-listed positive factors.
1) Working on Nagios Core for more than 10+ Years.
2) Good Hands On skills to cover the standard monitoring parameters such as CPU, Memory, Storage & Running Services.
3) By introducing NCPA Agent, further monitoring became very smooth & saves time as NRPE & NCPA Client Side Configuration takes more time. On the other hand, NCPA Installation is very straight & you just need to provide a unique token only.
4) NCPA Agent is available for Windows & Linux like OS environments with most of the current & previous stable kernels.
5) Presently, more than 500+ nodes & 2500+ services are under active monitoring.
The monitored services are as follows.
1) Windows & Linux Nodes
* CPU Utilization (%) & Allotted CPU Cores.
* Memory Utilization (%) & Allotted Memory (MB/GB/TB)
* Total Storage Utilization, Allotted Storage Space & Available Storage Space (MB/GB/TB)
* Running Services, CPU & Memory Utilization (%) by a particular service.
* Start the monitoring service if Nagios finds it SHUT.
2) Cisco Nodes (Switches, WLCs, APs, Routers)
* CPU & Memory Utilization.
* Bandwidth Utilization (Combined & on individual interface as well).
* Cisco WLC: No. of connected APs, CPU & Memory Utilization & Bandwidth Monitoring.
* PING RTA, Jitter & Packet Loss.
* Temperature, Free Interfaces, IOS Version, Switch Stack Status.
3) Services
* DNS/Domain Name Expiry
* SSL Expiry
* Many More...
How has it helped my organization?
By integrating below-listed add-ons with Nagios Core, the end-to-end monitoring become more useful.
1) PNP4Nagios
2) NagVis
3) Nagios BPI
4) NagView
5) NagDash
6) check_mk livestatus
What is most valuable?
I started working with Nagios Core when RHEL 5 was there & since then it is still in functioning mode various types of hosts and services have been configured such as the IBM AIX, Linux, Microsoft Windows, Cisco Routers, WLCs, Switches & certain gateway level firewalls. (Fortigate, Juniper Netscreen, Checkpoint, Radware AppDirector Load Balancer)
As my knowledge gains, I've started deploying additional plug-ins (as stated above) to have a productive monitoring environment.
Please Note: Nagios Exchange is a great source of plug-ins for testing purposes.
Nagios is still functional & doing well after many years despite having 500+ nodes & 2500+ services. Moving further, the Nagios HA pilot project is in progress to have a high availability & business continuity.
In opposite to Nagios XI, Nagios Core needs to be configured through a shell console only. Though open-source GUI Content Management tools are available I'm good @ shell level only.
Using NCPA, We monitor active & passive checks both. However, Active checks mostly work well in my architecture.
The biggest difference between Nagios Core & XI is, everything comes pre-built with Nagios XI, while for Nagios Core, all add-ons need to be configured individually.
So, Nagios Core Engineer/Administrator requires in-depth shell-based knowledge & a clear understanding of Nagios Structure for all kinds of troubleshooting.
What needs improvement?
Provide a user-friendly GUI to configure various hosts/services using a graphical frontend.
For how long have I used the solution?
I have been using Nagios Core for 11 years.
What do I think about the scalability of the solution?
Nagios Core Scalability should be a serious concern for IT professionals responsible for overseeing their unique hosting environments.
Presently, my stand-alone Nagios Core engine monitoring 1000+ nodes but from the scalability point of view, I'm going to perform a distributed monitoring environment in HA (High Availability) mode. Single Nagios Core stands of SPOF (Single Points of Failure) having high RTO & RPO.
Nagios Core, being an open source, contains limited measures you can take to increase the scalability of the product. As it said, a free monitoring tool will simply not be able to handle the volumes of a more flexible, robust system.
That's why keeping Nagios Core due to the $0 price tag may seem like a cost-efficient approach, but eventually, it becomes mandatory to scale it without impacting productivity.
How are customer service and support?
Nagios Core, which is an open source product has very limited scalability features. Large Nagios solutions have bigger problems as the Nagios core doesn't provide much scalability until you design a decentralized architecture.
Basically, Nagios uses a group of remote servers & services that are configured to perform various kinds of checks. This design makes Nagios difficult to scale, as large fleets quickly reach the limit of vertical scaling, and Nagios does not easily scale horizontally.
For me, I've configured a total of 7 different Nagios Core Servers to monitor hundreds of nodes. Using this methodology, I can be able to cover different groups of infrastructure & all those Nagios Core Servers transmit real-time data on an independent Nagios dashboard tool named MNTOS (Multi Nagios Tactical Dashboard System).
Here, I just need to monitor the MNTOS Dashboard which shows all statistics & can jump on that Nagios Server directly if MNTOS shows any kind of WARNING/CRITICAL Alerts.
In summary, you need to put too much effort to scale Nagios Core to justify organization's actual requirements.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I tried using zabbix earlier, however, I was much more confident with Nagios just because of its vast community-based plugins, and active community support, even you can have Nagios Core Paid Support by paying approximately 2200 U$/year.
Some of my known Nagios Community Members have started deploying check mk product but still I stick to Nagios Core.
How was the initial setup?
Setup is straight-forward & well documented.
What about the implementation team?
I'm the only person who manages Nagios Core & relevant services. Once deployed, I provided training to some Linux engineers so that they can manage it during my unavailability.
So, everything is in-house. Also, we have a roll back option to restore the last configuration if something goes wrong. In most cases, junior Linux engineers make a mistake in Nagios host/service configuration files. So, prior to making any changes, they need to make a backup copy under the same directory level.
What was our ROI?
Saved millions of rupees just because of Nagios Core. Else, a Tier-III Data Center requires a paid tool for end-to-end monitoring. Even, my organization endorses me for Nagios Core with an award.
What's my experience with pricing, setup cost, and licensing?
As Nagios Core is an open source product, you cannot earn money as a product.
However, you can earn for Nagios Installation, Configuration & Ongoing Support. In other words, setup cost for end-client & regular o&m support.
Other side, you can convert Nagios Core into Nagios XI by contacting nagios.com
What other advice do I have?
Nagios is really very good from the configuration point of view. If you have a hefty budget, go with Nagios XI else Nagios Core is equally good. Just you need to put a lot of effort to configure & monitor everything.
On a scale of one to ten, I would give Nagios Core a 10 out of 10.
Which deployment model are you using for this solution?
On-premises