Nagios Core 4.5.9 on CentOS 10

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.

Our main use case for Nagios Core on CentOS  is to monitor our server that holds our services data from clients and patients. We use a FIRE data structure. The data will always send messages to our client based on the condition of the patient. We have about 10,000 patients at that time.

Nagios Core on CentOS  helps us monitor our ecosystem health, our services, and our hosts on the ecosystem. We have visualized visibility on our hosts and services. When the service is degraded or there is an outage, we can fix it as soon as possible. Nagios also automatically tries to fix the data, and Nagios has an outstanding feature in that it can escalate to a manager when there are no actions or no mitigation solved on the incident.

Nagios Core on CentOS sends messages using a WhatsApp API. For urgent matters, it can send directly to the PIC on the server.

Nagios Core on CentOS has positively impacted our organization by increasing recovery between failures. We can keep our services up-to-date.

I don't remember the specific metrics or numbers, but since using Nagios Core on CentOS, there has been a very dramatic increase in our response to the latency on an incident.

The best feature of Nagios Core on CentOS is that it can handle many services using plugins. There are thousands of plugins on Nagios Exchange. At first we were thinking that we had to build the plugin for our needs, but there is a plugin available on Nagios Exchange.

We don't implement all Nagios Core on CentOS features, so I don't think we have a suggestion for the features since we didn't explore all Nagios features yet.

So far, it is enough regarding improvements needed for Nagios Core on CentOS. We don't have any ideas to improve Nagios Core on CentOS, even small ones.

Regarding Nagios Core on CentOS's AI capabilities, there are always updates from Nagios to meet regulations or protect against security attacks. We don't implement that AI capability of Nagios Core on CentOS. It is not fully implemented in our system, so we don't have any comment on that AI.

We have been using Nagios Core on CentOS since we migrated from AliCloud into GCP , which was about two years ago.

Nagios Core on CentOS is stable as far as we have experienced.

We can add many hosts and many services to Nagios Core on CentOS, so its scalability is great.

I don't think there will be scalability issues, but maybe in the future, since our organization and our ecosystem will get bigger, we will have to deploy a distributed Nagios, which will be something great to do.

So far, we haven't had any problems using Nagios Core on CentOS, so we haven't contacted customer support yet.

Previously, we didn't have any idea to use a monitoring system for our ecosystem, so we chose Nagios Core on CentOS in the first place.

We purchased Nagios Core on CentOS through the GCP  marketplace.

Unfortunately, we don't have that metric for the cost versus the return on investment with Nagios Core on CentOS.

Regarding my experience with pricing, setup cost, and licensing for Nagios Core on CentOS, it is not my responsibility to justify the pricing. I think it is quite fair.

We went straight to using Nagios Core on CentOS since one of our team members has a lot of experience handling and using Nagios.

I would rate Nagios Core on CentOS 8.5 out of 10 points.

The reason I chose 8.5 out of 10 for Nagios Core on CentOS is subjective. I believe it could be a higher score since we don't explore or implement all Nagios features at this time.

I highly recommend using Nagios Core on CentOS to monitor an ecosystem.

Everything is good regarding Nagios Core on CentOS, and everything runs smoothly as expected.

My main use case for Nagios Core on CentOS  is monitoring all the services of my customers, including CPU, RAM, different kinds of services, and certificates. With the trigger feature, I try to optimize the time and services. I also want the graphics displayed on TVs in the main room with my colleagues, with alerts that include sound and colors.

The best features Nagios Core on CentOS  offers include monitoring the servers of my customers, getting alerts into my email, and receiving disaster alerts at different times during off-hours and labor hours in my customer's environment to know if someone created a user or if something is happening on the servers outside hours and inside labor hours. The feature to put triggers outside business hours to send a script to block some IPs, some users, or restart any services stands out most to me.

Nagios Core on CentOS has positively impacted my organization by reducing downtime in systems because sometimes there are services that were down, and with a trigger, I can start them again. I can also send an alert to the users or to my companies to try to solve the problem.

I'm not reducing any employees, but I improve the times to solve problems with Nagios Core on CentOS. I also try to improve my tickets to the customer because I discovered things that Nagios tells me to solve. I have increased my company with Nagios Core on CentOS.

Nagios Core on CentOS needs to improve the templates to send messages to IT companies and also integrate with different systems or improve integrations with QNAP, Synology, Ubiquiti, and different applications.

The documentation is good, but the dashboards could improve and be more responsive or modern.

Graphics improvements that are similar to Grafana  are additional improvements that Nagios Core on CentOS needs, but it's adequate for me and it's working well.

I've been working here for approximately eight years. I've been using Nagios Core on CentOS for approximately five or six years in my position.

Since approximately one year ago, Nagios Core on CentOS is improving its reliability and accuracy to get nice precision to the different services and correct monitoring. Nagios Core on CentOS has been operating smoothly and running perfectly, and I have had no bad experiences with it.

Because I have this machine on-premises, I can improve the machine physically if it needs more RAM or more processor to update my machine and the requirements.

I have never used the CentOS  support for Nagios Core on CentOS technical support.

I used Zabbix  before Nagios Core on CentOS, and I changed to Nagios because it's better than Zabbix , and because it's easy to use and they have improved updates all the time.

I evaluated PRTG before choosing Nagios Core on CentOS, but it's so expensive.

My advice to others looking into using Nagios Core on CentOS is to study the knowledge base because sometimes you need to learn and apply the settings. I would rate this product an 8.

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.