Nagios XI Reviews

It's ability to monitor a good range of services out of the box and it's extensibility with the use of plug-ins, with an active user community sharing community contributed plug-ins to cover monitoring for a very wide range of services and components.

It's helped us to improve our incident management, problem management, and capacity management.

The web interface is perfectly fit for purpose but isn't up there with the best modern admin panels. There is scope for improvement to make it more dynamic and responsive.

I've been using it for three years.

Nagios XI ships as a virtual appliance and is easily deployed.

There have been no performance issues.

Clear instructions are provided on how to expand the disk capacity of the appliance and the solution can be scaled to allow several distributed Nagios monitoring instances to work together.

Customer service is excellent.

I haven't needed any technical support.

We previously used the free version of Nagios and decided that the commercially packaged version Nagios XI was well worth the cost and reduced the admin overhead significantly.

Initial setup is straightforward and allows monitored hosts to be added one-by-one using a wizard or added in bulk using the bulk add tool.

An in-house implementation was done. I would advise that you need to understand the overall basic architecture of Nagios before implementing it.

In my view this product is very good value for money when compared with other commercially provided monitoring solutions.

Implementation is best done by people with a good general Linux/open source skill set. If you have these kinds of people then implementing Nagios should be fairly straightforward. If you have a bunch of Window admins who've never touched a Linux system, then implementation could be a challenge.

Nagios enables you to choose to have either a single server structure or multi server net. This helps you get the best optimization in a non-local datacenters, or remote servers on subnetworks.

I once worked on a project for a consortium in a mixed setting with Windows and Linux machines. We have integrated Nagios servers in each of the 120 head offices with different specifications. It is used for the monitoring of more than 1300 servers and 16000 clients with different sub-networks and many different applications in a closed environment. The servers of their head offices were configured to propagate the data to the primary Nagios server of the main control center, and to this mirror in the operative center and to the mirror it in the disaster recovery center.

They need to develop a better integration with a common ticketing system will be great. Once I built a complete integration with OTRS:ITSM and Nagios using the Samba LDAP database as the registry for user and machines in the software. It was a complex setup, but functional and could probably work in an Active Directory environment as well, but a fully-functional bidirectional bridge engine will be great. Nagios Enterprise has Nagios Incident Manager software but sometimes you need to work on preexisting systems with strong customizations.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

Nagios is the best software of its kind if you have time for configure any host and network, and you can do quite everything with a bit of scripting. It is well documented, scalable and modular, as well as being good for a small business and for an enterprise environment. Take your time to study the product and test the agents first; be very careful on the traffic generated by agents and server-to-server communication.

Simplicity of configuration. I can set up configuration of 100 devices with about 10 services in one to two days.

I can track systems behavior and network failures.

It's in need of more standard plug-ins.

I've used it for around 12 years

We had no deployment issues.

The product is quite stable, and we've had no issues.

There's been no issues with scaling it for our needs.

I'm not using any customer service.

I'm not in need of any technical support.

I started with this product.

It's very straightforward initial configuration if you start with your distro packages.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

It's very simple, and is very valuable to us. If you need to monitoring your environment just do it

• Real Time Alerts
• Network Map

Our infrastructure is now under monitoring proactively and we don't have to wait for complaints from the customers/internal operation team to inform regarding any issue with the service.

3D datacenter view of the infrastructure to have more specific control of the environment and concept of 360 solution to monitoring is now emerging.

We've been using it for over a year.

There were no issues during the deployment.

We have had no stability issues.

We've not scaled it as of now.

As it's an opensource project, there is good contribution to, and good support, from blogs and FAQs.

It's a simple setup for a normal Linux users.

In-house. Its simple deployment but complexity comes once you have to import more plugins. Do check the required infrastructure support before deploying and check alerting mechanism.

The community edition is free, and for an enterprise deployment its costing is good compared to other solutions.

I have tested Zenoss, ManageEngine solutions - Op Manager and Application Manager. We chose Nagios over Zenoss mainly because of its lightweight interface compared to Zenoss and the ManageEngine free edition has limited nodes.

First you need to do a complete analysis of the nodes and your requirements before implementing Nagios for monitoring.

The monitoring and notification when an issue arises.

It was essential we had to have live monitoring as we were trial-ing a real-time communications application on a live site.

While the UI is functional, I have always thought there was room for improvement here. It is at times assumptive for the not so technical, rather than informative.

I've been using it for 12 to 18 months. Presently I work as a software test engineer and my employer has been using Nagios for approximately ten years now. I first used Nagios in January 2014. I was in a small startup company based in the TSSG called Kodacall, it was based around WebRTC. I implemented in order that we could monitor our network as we had some clients who very kindly were letting us test our product on their live site. I really found Nagios a perfect fit for us and a good product to work with. As the saying goes “It does exactly as it says on the tin”. I hope what I have given might be of some small help.

It was deployed as a stand alone tool and is also integrated with Docker.

It was deployed as a stand alone tool and is also integrated with Docker.

It was deployed as a stand alone tool and is also integrated with Docker.

I didn’t require any service as the documentation is good and most questions are answered on any number of forums.

Setup ran pretty smooth. It's not overly difficult but it does require patience and some experience would make it easier. Like everything it is easier the second time around.

We implemented it in-house.

Although we did look at other tools, we felt Nagios was a good fit for us.

I would have no hesitation in recommending it.

I think that the most important feature of Nagios is that you can write your own plugin, so you are able to create your monitoring system based on what you need.

For example, I'm using a backup system that writes in a file when it's done. If this file is empty it means that the backup fails: well i've written a Nagios plugin to check this so i can be sure if a backup is ok or not.

We're managing servers and services that needs constantly monitoring so I've implemented a monitoring system Nagios-based to alert me when something bad happens. For example, if a server goes down this system sends me a notification When a service becomes critical, it notifies me so i can check. This improve our time to handle problems and can make us proactive to customers.

I think that the community needs to concentrate development to get a standard GUI (Adagios is a side project) and gives the user a better notification system. For my system, I've developed the notifications because it basically just sends you an email.

I tested Nagios at university for seven years, and have been using it intensively for three years.

It has no particular needs or configuration to works well. Actually i'm using it in a virtual environment with a Debian-based OS.

There have been no issues with the stability.

We have had no issues scaling it.

I haven't had to use it.

I haven't had any need to use it.

Nagios setup is very simple. You can find some problem during plugin configuration or host configuration if you don't use a GUI like Adagios. If you use both it's easy to setup and configure your host and services.

I implemented it in-house.

The ROI is absolutely linked to time. You can save a lot of time using Nagios monitoring because otherwise you need to check all of your services or system one by one.

There are several alternative to Nagios like Icinga (which is a 2.0 Nagios son), Observium, and LibreNMS. If you need only an SNMP monitoring system or you need real time graph Observium is your choice but Nagios is a complete solution.

The only advice is to be patient and creative because you can control everything you can need with Nagios.

The product for which Nagios was used to monitor was:

• Brightmail back-end 7/24 Operation
• Brightmail heuristics engine and development infrastructure

The ability to write your own plugins is the most valuable feature, but also it's nice that you can rudimentary monitoring primarily for Linux systems right out of the box.

We spend less time verifying that everything is up and running as Nagios does that for us leaving us time to do the other things. When something does break Nagios directed you quickly to the cause. With Nagios enabled, disruptions were less frequent and attended to more quickly.

Scaling Nagios to cover multiple regions or data-centers is challenging. It requires another tool which I never incorporated. Due to this gap I used a dedicated Nagios servers within each specific operation.

I've used Nagios since 2000. Before that it was called BigBrother and NetSaint which I hadn't used.

Implementation on Windows was painful. Also the use of NRPE can be problematic as its generally not inherent is OSes.

We have had no issues with the stability.

There have been no issues scaling it.

I didn't use customer service and technical support for Nagios. Everything I did I learned online through the extended community.

Prior to using Nagios for monitoring we had grown our own monitoring solution which latter became the company NOCpulse and was picked up by RedHat. Previous to that I used various other homegrown monitoring methods.

The initial setup is straightforward, but you need to have a good grasp of the underlying files structure. All the pieces are there but without this understanding where to put things is not entirely intuitive.

I always installed Nagios by myself. I never used a team. Advice I would have is you need management buy in. More than a few times I would implement this solution but without managements support it got little traction upfront. Meanwhile management pursued pricey solutions which were cumbersome and had long implementation cycles.

I can implement Nagios is a day for a medium sized (500 units) operation. Since the cost is zero and it can use a fairly cheap server to run on the ROI is nearly immediate.

Currently I use New Relic and Munin to track and maintain the operation I run. New Relic however isn't designed to alert like Nagios and they have told me as such.

Find a site where Nagios working and look at their implementation. Understand the file structure, dependencies and implementation. Start with the basics and add as needed. Identify what needs to be monitored and why.

Also, Nagios does not do trending/graphing well. I used the Nagios version of MRTG and it was pretty awful. I incorporated Cacti which partners well with Nagios. Without both tools you don't have a good understanding of how your operation is functioning.

We must separate the 2 parts of this product :

Monitoring Core (Nagios Core) -

Possibilities to manage Nagios Core and Nagios Client configurations by Service Manager like Ansible, Puppet etc. For big environment's, it's the simplest way for industrialisation

• Correct and scalable Dashboards for management
• Easy way to view you entire production ( more complete than Nagios Core interface)

My customer choose this product because he previously worked with Nagios Core 3 and didn't know other tools. His principal argument for him is that the Dashboards correctly present their work.

The important separation between Interface and Core to maintain historical plugins and methods generate complexity that makes Nagios unusable for repeat work. You must choose a way to manage your configuration, by interface or by files in Core, and never change your rules. If you choose files, you lose the dashboard advantage instead of importing them manually, and, for the moment, there are no APIs for managing hosts/services are present. If you choose Interface, you must configure hosts/services manually, and again there are no APIs for managing hosts/services are present.

Nagios Core has a big advantage in that has been lost in Nagios XI. Another way you could manage is by having three different databases

1. Postgres for Nagios XI's hosts/services définitions
2. MySQL with ndo2db for metrology
3. Rrd for the Nagios Core

This is not easy to maintain and High Availability becomes complex. The simplest way is by VMware HA modifications preconfigured by Nagios.

I've been using it for the last six months.

It's very easy to install it and manage it with Nagios XI's interface.

There have been no issues with the stability.

I only have 50 hosts and haven't needed to scale beyond that.

Nagios responds quickly when you need them, and the community is really big.

I previously used HP SiteScope, Nagios Core 3, Xymon and Zabbix. I didn't choose Nagios, my customer choose it and I implemented it. My prefered tools is Zabbix for the moment.

It's very easy for the basics features, but, like others tools, when you need plugins, it becomes more complex.

We did it in-house.

No ROI was requested by my customer, only visibility by their management and using their knowledge on Core 3.

Your architecture must be conceived prior to implementation as each error must become complex to change.