Nagios XI Reviews

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.

Nagios is an open source monitoring tool for monitoring network services. Installation is quite easy and the interface is user-friendly and configurable. We can monitor disk space, CPU utilization, memory usage, host availability, NFS availability and a lot of other things. Due to its extensive features, it is widely used in IT markets.

We used to get the system hung. After monitoring implementation, we keep on getting alerts for CPU, memory and other things. So, we take care of servers now before it goes to hung state.

Nagios provides most of the features by default, however to add more services to it, it requires additional plugins which require little effort on administrative end. So far, clustering and failover of Nagios is not available-- development is still working on it.Highly recommended tool for monitoring services.!!

I have been using Nagios for 4 years now and still using it.

There were no issues faced during deployment. It was pretty handy and most of its docs are generally available over the internet.

Alternatives Vendors: Zabbix, Opennms, Zenoos, Cacti !!

Nagios is our cloud-based monitoring system. We need to deploy it and integrate with our CRM, customer portal and the ticketing system as an end to end customer support platform. We use it for monitoring and gathering data from our customer service equipment.

We have more than 100 people using the solution and 3 people to do the maintenance.

Nagios XI has a custom API feature, and we can expose custom APIs for our integration. This is a great feature.

In fact, Nagios XI grant access to administrator to use official common backend commands and callback functions developed by Nagios in custom APIs, so custom APIs could be created as an standard web services without degradation in performance and access to needed data easily. This APIs will be registered and listed in Component Management and administrator could be able to manage them as well. Also, Authentication will be done by creating unique Token for each user created in Nagios XI User Management automatically and it could be used in calling each APIs to manage access level of caller user.

All documentation and examples about creating custom APIs are available in "Help" tab in monitoring GUI and each person with moderate level of knowledge about development in PHP language  (Needless to say it required admin privilege), can create this kind of web services. 

We often need to develop custom plugins to get Nagios to work the way we want it to work because the features we need are not always available in Nagios. Some products such as Zabbix have a software monitoring system built-in, such as the Prometheus monitoring system. It can use the features to monitor cloud systems. This would be a useful feature to include in Nagios XI. Nagios has some plugins to monitor clouding systems, but this feature on Zabbix is so handy and so user-friendly. I think it can be added to the Nagios monitoring system.

Nagios is stable, but we are using mod-Gearman for distributing the solution. There is network limitation on this, such that if the network is not stable, the whole solution is also, not stable.

Because we are working in Iran, we have embargoes, and this means we don't have any support from Nagios support. As a result, we have to use self-study. We research using Google and nagios forum this has helped us to resolve our issues.

Set up in Nagios is complex. However, it's okay once you have done this task a few times, so you understand the logic. Once you have done that, it is easy to use.

We also compared the product to Zabbix.

I would recommend this solution because it's so powerful with no limitation, especially when using the XI version. I would rate Nagios 8 out of 10. Overall, I find it to be a very good solution.

• The integration with the alerting software 
• Automated maintenance windows 
• The ability to set up templates and groups of checks, as well as customize the checks themselves.

We receive alerts for services and servers experiencing problems throughout the day and night, so we can maintain 24/7 monitoring.

Improve the documentation, examples, and best practices, therefore users can understand how to do things. Luckily, I had someone teach me the ropes, but to newcomers without someone to train them, it would be very difficult to learn.

Around two years.

Generally, it is very stable platform. Occasionally, we have to restart the monitoring engine, but it is very easy to do.

Adding new servers and passive checks (which require setting up agents and NRDS) on servers are a little difficult to do properly when employees don't understand the process. Since documentation is lacking, it's a matter of trial and error before things work properly. So yes, scalability could be improved.

We did not purchase support, therefore building the entire platform in-house. This has probably led to us not using best practices.

It's generally good, but lacks documentation.

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.

We have installed  Nagios Core and Nagios XI on many customers in Latam successfully. A good use case was one customer with many servers (upper 1000) and many routers and switches (upper 2000), they wanted to monitoring operating systems and switches ports, Nagios worked like to swiss watch.

With Nagios, I can monitor since a phone on a desk to very big servers of any company. Also, I can monitor a software made in-house to software of bigger companies. Nagios is great for verify quality and quantity in a datacenter. Nagios can show if there are problems showed behavior in datacenters.

The community, Nagios XI is made on Nagios Core base, and the community makes plugins on almost any language of programming. Nagios is not owned by any brand.

The second feature is Nagios is very friendly, if you can customize the tool to the specific environment.

If you want the best security: Log Server is better. If you need in-depth networking, I recommend Network Analyzer. If you want any other implementation of Nagios, the best is Nagios Fusion.

More than ten years.

Nagios is very stable, We haven't reports on problems with the Nagios servers in never opportunities.

You should be careful when you monitor many hardwares with many softwares, the performance of one license could be compromised. You need to manage more than one license if you have an infrastructure which is very large.

10 out of 10.

Yes, I have used other solutions. I switched to Nagios, because Nagios is not linked with any brand that's independent. This is good because you can monitor any brand of switches, routers, servers, central phones, etc.

The initial configuration is very easy. The complex is customizing the solution.

We are an expert consultant, who implements for customers.

It's complicated answer this question, but the ROI depends on Datacenter.

It is good to contact experts for advice about what is the best solution for your specific infrastructure and enterprise.

I evaluated Zenoss, Zabbix, SolarWinds, and other solutions.

You will need an expert consultant for the best implementation.

I mainly use Nagios XI for critical UN, for example, if the CPU usage is very high.

It can be quite difficult to know which drivers and agents to use when setting up.

I've been using Nagios XI for around five years.

Nagios XI is stable.

Nagios XI isn't really good for scaling, in my experience.

The initial setup is very complex, as there's no helpful manual and there are a lot of custom settings you have to learn.

Learning to use Nagios XI is quite time-consuming, so you need patience to get the best out of it. I would rate Nagios XI six out of ten.