Nagios Core on CentOS Reviews

My main use case for Nagios Core on CentOS is checking disk usage, services, and load of the server.

A specific example of how I have used Nagios Core on CentOS in my environment is when I had one server that was a standard server that had been shut down due to server load, and with the help of Nagios Core on CentOS, we checked the basis of the issue, which was helpful.

The database services had been down, and we received help from Nagios Core on CentOS in addressing that situation.

The best features that Nagios Core on CentOS offers are that we can add services in the configuration files, and we have post-monitoring with a manual that checks for about thirty items.

Nagios Core on CentOS has impacted my organization positively because it is impactful to the business. If the production server is down, Nagios Core on CentOS will check certain services, which impacts production.

Regarding specific outcomes, Nagios Core on CentOS has helped reduce downtime. The downtime for the production service that was down took only one hour, which is helpful for our organization.

To improve Nagios Core on CentOS, we need to consolidate the many pages we see on the interface into a single page because we cannot check information across multiple pages efficiently.

I have been using Nagios Core on CentOS for two years.

Nagios Core on CentOS is not stable.

The stability issues I have experienced with Nagios Core on CentOS are that we need to make it a single page interface, similar to Zabbix.

I did not take help from customer support for Nagios Core on CentOS, as we manage it on our own.

I did not previously use a different solution before Nagios Core on CentOS.

My experience with pricing, setup cost, and licensing is that it is good, with very cheap costs, and licensing is very easy for the organization.

Before choosing Nagios Core on CentOS, I evaluated other options, specifically Zabbix.

My advice for others looking into using Nagios Core on CentOS is that it is good, but we should set only one page for the services and disk devices. I would rate this product an eight out of ten.

My main use case for Nagios Core on CentOS is monitoring my IT infrastructure, including servers, network devices, and critical services.

A specific example of how I use Nagios Core on CentOS in my daily operations is checking if a service has stopped or a server becomes unreachable; it automatically sends me an email so I can investigate and resolve the issue quickly. In another scenario, I monitor disk space and system performance on Linux servers and Windows. It is configured to alert me when disk usage exceeds the defined threshold, for example 80% or 90%, or when CPU and memory use remain high for an extended period, which helps me investigate where a problem exists and prevent outages caused by full disks or overloaded systems before they affect users or applications.

Nagios Core on CentOS has positively impacted my organization by moving our time toward a more advanced and modern monitoring solution, resulting in a better dashboard and tools to view system health in one dashboard and also optimizing alert handling.

The best features Nagios Core on CentOS offers are the flexibility to use it for monitoring servers and also using a plugin to check specific services, backup VMs, or other specific checks on my servers, so if there is any error on disk or CPU or high usage of CPU or disk, it helps me have a powerful alerting system and a high level of customization; therefore, the best feature is the flexibility through plugin-based monitoring.

Out of the flexibility, server monitoring, customization, and plugin support, I rely on server monitoring the most in my day-to-day work, and it makes my work easier by providing timely alerts about server status.

One area that could be improved in Nagios Core on CentOS is the user interface.

I have been using Nagios Core on CentOS for approximately ten years.

My advice for others looking into using Nagios Core on CentOS is to start with a very clear monitoring plan before installing anything; define exactly what you need to monitor, servers, network devices, and what metrics truly matter, as this will reduce noise later and keep the system useful.

Regarding Nagios Core on CentOS's security capabilities, it is generally considered solid because it is based on a simple architecture, core, and plugins, which reduce the attack surface; security is managed through standard Linux hardening, firewalls, limited access, SSL for the web UI, securing the web interface, patching, Nginx authentication, and restricting plugin execution permissions, while also keeping systems patched.

Regarding Nagios Core on CentOS's accuracy and reliability of output, it depends on rule-based checks and plugin configuration rather than intelligence, as Nagios Core on CentOS itself does not have native AI capability.

I primarily use Zabbix for monitoring purposes, but Nagios Core on CentOS acts like a safety belt for all the system cloud and on-premise systems.

I have many CentOS applications running, which include Java apps, and for their VM specs, CPU, memory specs, and other operating system alarms, I use Nagios Core on CentOS for all of them.

Nagios Core on CentOS serves as a safety belt because when I lose the entire cloud and also monitoring tools like Zabbix, Nagios Core on CentOS always lets me know that.

For example, when I lose the cloud environment, Zabbix misses that because Zabbix was also on cloud, but Nagios Core on CentOS saved us.

I'm not monitoring Nagios Core on CentOS from Zabbix, but I could also monitor Nagios Core on CentOS from the Zabbix side, though I haven't done that yet.

Alerting in Nagios Core on CentOS is instantaneous and more accurate. The accuracy and reliability of Nagios Core on CentOS's output are quite good, and I have always used it on CentOS, so it has been reliable and accurate.

For example, when I lose the cloud environment, Zabbix misses that because Zabbix was also on cloud, but Nagios Core on CentOS saved us.

Handling upgrades and patching for Nagios Core on CentOS is straightforward. I use the upgrade documentation on GitHub, which is simple to handle, and I haven't faced any challenges or errors during upgrading.

I have about 150 endpoints, but even though it is on low spec servers, Nagios Core on CentOS has no lags or slowdowns and is quite fast.

I have only a few critical and important alarms with Nagios Core on CentOS, so I have no cases of false positives.

Nagios Core on CentOS could use a better UI.

Documentation for Nagios Core on CentOS can be improved.

The learning curve for new users adopting Nagios Core on CentOS is challenging, primarily due to the limited documentation available on the internet regarding how to install and maintain it.

I have been using Nagios Core on CentOS for about five years.

In my experience, Nagios Core on CentOS is quite stable.

I already have many endpoints, but I don't need any scalability because the number of my endpoints is fixed and not increasing.

I have never needed to reach out to customer support for Nagios Core on CentOS.

Nagios Core on CentOS is the first monitoring tool I have installed.

The easy to install feature of Nagios Core on CentOS is very simple.

For example, Zabbix is more complicated on the agent and server side, but on Nagios Core on CentOS, NRPE and Nagios server are much easier to install and maintain for me.

Time and money are examples of ROI benefits because when there is a disaster in cloud or on-premise systems, it means loss of money and time. Nagios Core on CentOS lets me know about these issues, and I can recover the system or stop the disaster, saving both money and time.

My company is using the open-source version of Nagios Core on CentOS, so there were no pricing, installation, or licensing costs.

I evaluated Zabbix and also installed it, so I am using multiple monitoring tools: Nagios Core on CentOS and Zabbix.

I am the only user in Nagios Core on CentOS as the admin user, so I have no idea about user access and permissions management.

When I see alarms on Nagios Core on CentOS, those are critical and important ones that would indicate an actual disaster, so Nagios Core on CentOS helps me only with alerting. The rest of the process is system recovery, which won't be straightforward, but Nagios Core on CentOS helps me understand the issue.

My advice to others looking into using Nagios Core on CentOS is that they should use a safety belt approach because using Nagios Core on CentOS as a safety belt in monitoring makes it the best option. I would rate this product a seven out of ten.

My main use case for Nagios Core on CentOS was monitoring my production environment. We had applications that included Apache and Tomcat applications, as well as databases such as MySQL, PostgreSQL, Oracle, and MariaDB, in addition to system load monitoring.

The best features Nagios Core on CentOS offers is that it is completely open source.

I have been using Nagios Core on CentOS from my first years onwards. Recently, I migrated from CentOS to Ubuntu and Red Hat.

CentOS support has ended, which forced us to use RHEL as well as Ubuntu. The main concern is that CentOS support has ended and its life cycle has reached its conclusion, which is why we moved over to other operating systems.