Nagios Core on CentOS Reviews

I am using Nagios Core on CentOS for monitoring, and it is primarily used for monitoring the IT infrastructure like servers, applications, and network devices. It will provide alerts and performance status, so I can detect and resolve issues before they become critical.

For the servers, we have already configured Nagios Core on CentOS, so it will help me to monitor CPU usage, MySQL database availability, network latency between CentOS and external endpoints, SSL certificate expiry, and performance visibility. I can set up alerts and see the same in the dashboards, response time, and all those things. It will also help me monitor the web server.

Regarding a customized challenge, there was one case scenario where the server was continuously hanging, which caused many issues for our customers. During that time, we set up Nagios Core on CentOS on the CentOS server. We got a real-time scenario and provided some particular use cases and critical scenarios. In that case, it helped us a lot to find out what the issue was. Other than basic monitoring, we can use custom plugins. I was able to run my scripts in Python, and it helped to do disruptive monitoring. Also, whenever Apache fails, it will automatically restart Apache or clear the cache whenever a memory spike is happening. We can check this during batch jobs that were scheduled at night. We set up a particular scenario where it should allow higher CPU usage during the batch jobs at night. It helped with the integration with Grafana for visualization, so it helped a lot. We also group multiple checks into a single business service. For example, the e-commerce site depends on the web server, database, and payment gateway. It helped to run all those things. This is the main scenario regarding the custom plugins, event handlers, and integration with Grafana to visualize the response time across the services and group all services into the business process called customer portal. We know if the entire app is healthy or not.

Regarding monitoring, it is a common feature with Nagios Core on CentOS. The best features I felt were the extensive plugins. There were hundreds or thousands of readymade check plugins. It is the ability to write my own scripts for anything unique to my environment. The main feature is that I get notifications by email, SMS, or integration with escalation policies, so the right person gets the right alerts at the right time. That is the main thing. The web interface, particularly the Nagios Core on CentOS dashboard, is user-friendly, and we are able to view the status, logs, and trends. That helps us a lot. It also automates fixes. For example, as I said before, if the high CPU usage comes in the night, it will allow it. If any particular batch jobs are running, it will allow the high CPU usage, and it helps to automate the restart of services, clear cache, or trigger scripts whenever an issue arises. It also scales across multiple sites and data centers, feeding results into the central Nagios Core on CentOS instances. Also visibility and control. The dashboards and reports give us a clear picture of the system's health, so it helps a lot. Mainly, as it is open-source software, it is free to use, and these many features are included, so it is a value-added thing. Our customer was very happy because he is very concerned about the budget. Due to that, he needed a free tool, so Nagios Core on CentOS helped us a lot to accomplish his requirement with great satisfaction.

Nagios Core on CentOS is very stable, and we are very happy about that one.

Nagios Core on CentOS is very scalable because whenever new servers have been added, we can add the service without any issues. It reduces repetitive configuration when monitoring hundreds of hosts and services. Multiple Nagios Core on CentOS instances can monitor different regions and data centers. It helped a lot. Because of this, it improves performance under heavy loads. It also automates fixes and prevents manual interventions. It helped a lot, and we are very happy about Nagios Core on CentOS's scalability and efficiency.

I will definitely refer Nagios Core on CentOS. First of all, it is free software. Second, it is reliable and scalable. It is very scalable whenever we are adding new services and features. Because of that, we do not need to worry. If we configure everything at the first time, we do not need to spend so much time on Nagios Core on CentOS. Because there are no license costs, it is ideal for startups and mid-sized companies. One of my friends has a startup company, and I referred Nagios Core on CentOS to him. Because of the thousands of plugins, he is very happy about it. Because of the monitoring, flexible alerting, and scalability, I will definitely suggest Nagios Core on CentOS to others.

Regarding this review, you have asked about the Nagios Core on CentOS integration. As I said before, because of the high reliability, high scalability, the plugins, and overall being open source, it helps a lot to monitor our systems, and it helps us a lot regarding our proactiveness.

Regarding complexity, I think there is no feature like InfluxDB AI, so it may require more expertise to configure. There are also some migration challenges in adopting the new dashboards, so it takes some time to train the staff, but it is not a big concern. I think it is better to add some advanced features. I do not think there are so many things that need to be improved in Nagios Core on CentOS. If it is better to customize the dashboard or if we can get something like a modern view, it will be helpful for the dashboard. I felt very happy with Nagios Core on CentOS.

Why I took off one point is that I think it is better suited for a small or medium setup. If large enterprises can use Nagios Core on CentOS, it will be helpful. It also requires manual editing of the config file, so it is a little bit time-consuming. The web interface is functional, but compared to some other latest AI monitoring platforms, it is a little bit lacking. I think the AI platform would score higher, but it is good. The reporting is just basic, so if we compare it with Grafana, it needs richer insights.

At most times, we did not reach out for customer support because there are community forums. Active users were posting newer issues, and they will post the solutions also. Community forums helped us a lot. Because of the documentation regarding installation, configuration, and troubleshooting, it helped a lot and avoids confusion. In recent times, we did not contact Nagios Core on CentOS customer care. We usually use the community forums, documentation, etc.

I think we have used Datadog for monitoring. It cost around, I do not remember how much, but it is more than $1,000, within $1,000 to $5,000, I think. Because of this, we were able to save that much money.

Nagios Core on CentOS is not just a technical tool. I feel that it helps the business grow a lot by reducing downtime and improving visibility. Because of this, we were able to perform proactive actions, which strengthens both operational efficiency and customer satisfaction. Previously, we were manually monitoring everything, so it caused many issues and manual errors, and we lost a lot of time. Automatic monitoring helps us to save many hours per week for the system admins. Because of the instant alerts, it helped us find an issue within minutes. Otherwise, it would take hours to find it. Problems are detected and reported immediately, which helped a lot. Because of the automation, automated recovery actions such as if an HTTP service or some other service fails, it will restart automatically. It can cut the troubleshooting time, so we can avoid P1 and P2 issues, and later we can check the logs and find the issues. We use the time to find the reason. It helped us a lot in improving efficiency and our mental health. The dashboard, as I said, was very clear and good. It is one interface for all hosts and services, so it is a best feature, and it saves time compared to logging into multiple systems. Reporting automation also helps us keep the SLA and uptime reports. Uptime reports are generated automatically, so it saves us from gathering manual data. Before Nagios Core on CentOS, we spent around ten to fifteen hours per week on manual checks for all services and everything. But after Nagios Core on CentOS, because of the automation, it is reduced to two to three hours. I think that is roughly forty to fifty hours per month.

It is deployed on-premises as well as in the cloud. We are using Nagios Core on CentOS in the AWS cloud. We are also using it on-premises. On the basis of cloud, we are using Nagios Core on CentOS on AWS. We have directly deployed Nagios Core on CentOS in AWS.

Regarding Nagios Core on CentOS, it is completely free. So we do not need to spend any money on that one. I think Nagios XI has some payment, but I have not used it until now, so it did not cost any money for spending on Nagios Core on CentOS. I think everything is good regarding Nagios Core on CentOS.

If it goes well this way and if Nagios Core on CentOS can keep the stability regarding the licensing, meaning the free software, the scalability, and the additional thousands of plugins, if Nagios Core on CentOS keeps improving as they have done for these many years, we are very happy about that. I am very happy to continue the Nagios Core on CentOS usage to monitor my service and do the scalability. It will help me a lot to find out the issues, and it helps me regarding my proactiveness. I give this product a rating of nine out of ten. Please continue maintaining this high standard, and I am very happy about Nagios Core on CentOS usage.

I used Nagios Core on CentOS at my previous company, Infosys, for three years. My main use case for Nagios Core on CentOS was monitoring servers. I used Nagios Core on CentOS as a monitoring server to monitor both Linux and Windows environments, and the setup was plugin driven where we configured host and service checks for CPU, memory, disk usage, and critical services such as SSH, HTTP, and database processes.

Nagios Core on CentOS was very effective in proactive monitoring, with its strengths lying in early alerting and flexibility through plugins, which helped us detect issues before they impacted users.

The biggest strength of Nagios Core on CentOS is its plugin architecture, which is extremely flexible because plugins are scripts or binaries that return a standard output and exit code. This means we can monitor almost anything, including system metrics, applications, APIs, or even custom business logic.

The flexibility of Nagios Core on CentOS plugins is one of the biggest advantages, allowing companies to extend monitoring beyond standard infrastructure into application and business-level monitoring.

Using Nagios Core on CentOS had a significant positive impact on the organization at Infosys where I used it by improving system availability, reducing downtime, and enabling proactive issue resolution. Nagios Core on CentOS helps organizations detect issues before they become outages. We were reaching out after users reported issues before; with Nagios Core on CentOS, we identified problems before users even noticed them. Automated alerts ensured the right team was notified immediately, and it worked very well for the organization.

Manual monitoring efforts were reduced, allowing the team to focus on improvement instead of constant checks. While Nagios Core on CentOS provided strong monitoring capabilities, it requires manual configuration and maintenance, which need proper planning and standardization in large environments. Nagios Core on CentOS transformed monitoring from reactive to proactive, improved system reliability, and helped the organization maintain better uptime and performance, reducing critical incidents by approximately twenty to thirty percent after implementing proactive monitoring.

Nagios Core on CentOS is very stable and reliable, but it can be significantly improved in terms of automation, scalability, and usability. Most improvements for Nagios Core on CentOS revolve around reducing manual efforts and modernizing the ecosystem.

Automating Nagios Core on CentOS configuration reduces human error and improves consistency across environments. Visualization is a major gap here, as modern tools provide much better dashboards compared to Nagios Core on CentOS.

For large environments, scaling Nagios Core on CentOS requires additional architectural planning, and tuning alerts is critical; otherwise, teams start ignoring notifications. Integration of performance metrics helps move from reactive to predictive monitoring, but having too many custom plugins makes it hard to maintain.

Nagios Core on CentOS is extremely powerful and flexible, but it requires effort to modernize with automation, better visualization, and a scalable architecture. It can still be very effective compared to newer monitoring tools, and it could benefit from a UI with tools such as Grafana, implementing distributed monitoring for scalability and fine-tuning alerting to reduce noise. These kinds of improvements would make it more efficient and easier to manage in large environments.

Nagios Core on CentOS is strong technically but needs ecosystem improvement to match modern observability tools.

I used Nagios Core on CentOS in my previous company, Infosys, and I used Nagios for three years.

Nagios Core on CentOS is stable and reliable, especially for long-running monitoring environments, but due to UI issues, we are moving to Grafana.

Nagios Core on CentOS is moderately scalable, working very well for small to mid-size environments, but scaling to large environments requires additional architecture and planning.

For Nagios Core on CentOS, customer support is community-driven rather than vendor-driven. Since it is an open-source product, support is good but not instant compared to enterprise tools. I was not entirely satisfied with the customer support, but it is acceptable because it is community-driven.

Before moving to Nagios Core on CentOS, we were using basic monitoring tools such as manual checks and simple scripts, and in some areas, we also evaluated tools such as Zabbix and SolarWinds. Ultimately, we decided to move to Nagios Core on CentOS, and recently, we moved to Grafana because the UI is much stronger there.

We definitely see a positive ROI using Nagios Core on CentOS, as while it does not have licensing costs, the real return came from reducing downtime, faster issue resolution, and improved operational efficiency.

Nagios Core on CentOS has no licensing cost since it is open-source; however, there are indirect costs related to setup, maintenance, and scaling.

Before finalizing Nagios Core on CentOS, we evaluated several other monitoring tools such as Zabbix, Prometheus, and in some cases, SolarWinds.

If you are considering Nagios Core on CentOS, then treat it as a powerful but hands-on tool. You will get great reliability and flexibility, but you need to plan for setup, automation, and maintenance from day one. For a mid-size or small size infrastructure, Nagios Core on CentOS is a good option; for a large infrastructure, consider other tools. I rate this product as a six out of ten.

Nagios Core on CentOS is used for monitoring systems and applications. We are using Nagios Core on CentOS for monitoring our servers such as Linux servers and Linux boxes, and we are also using Nagios for application performance.

Alerting is a very helpful feature of Nagios Core on CentOS because it has various features like infrastructure monitoring, alerting and notification, and service monitoring, which help us to send alerts and monitor the whole infrastructure. There is also monitoring of services, such as HTTP and SSH monitoring, which we can do from Nagios. The dashboard and reporting are very neat and clear in Nagios, so those features are helpful to us for monitoring the infrastructure as well as the application.

We can integrate Nagios Core on CentOS in the CI/CD pipeline, which reduces downtime, identifies root causes faster, and handles events. Event handling and automation are also done in Nagios. Nagios Core on CentOS has reduced downtime because it helps us to identify the root cause faster. We can then proactively detect the issue, and after that, we reduce our SLA compliance, so I believe it is helpful for the organization.

Before Nagios Core on CentOS, we were getting alerts after the incident happened. After implementing Nagios and integrating it with our existing system, we get alerts in real time. If an incident happens, the next second we will get email alerts through the Nagios alerting feature, and then the instant alert supports the team, allowing us to easily identify the root cause and reduce mean time to repair. This is how Nagios helps us to reduce the SLAs and other issues.

Nagios Core on CentOS is a very good product in design and people will use the dashboard. It has a simple dashboard, so it is easy to use.

I would like to add some features to Nagios Core on CentOS. In the modern world, we need Kubernetes and OpenShift support for Nagios, and it would be better to support the Kubernetes and OpenShift platforms. Container monitoring can be improved.

It has been two years that I have been using Nagios Core on CentOS.

I chose a rating of nine out of ten for stability and reliability because it is very stable, but something needs to be improved for the stability.

We have not seen any challenges with Nagios Core on CentOS. Its scalability is overall good for medium and large enterprise environments, though it requires tuning at a very large scale.

The customer support for Nagios Core on CentOS is good for the end customer, including both community support and enterprise commercial support. For community support, we go to the Nagios Core website and provide our issues there. For enterprise support, we go to Nagios XI, and with a commercial subscription, technical support from the Nagios team provides us with solutions if we are having issues. Enterprise support provides assistance for installation, upgrade guidance, and troubleshooting configuration help, while community support offers benefits like free resources, a large user community, and many existing solutions online. We work in an organization with enterprise support, which makes it very good support for the end-user customer.

I advise others looking into using Nagios Core on CentOS to choose it for strong infrastructure monitoring if they want reliable alerting, and if they want on-premises or hybrid cloud, both are supported by Nagios Core on CentOS. There is also a low-cost solution and custom monitoring data, and it works for both data center and enterprise infrastructure. If these features are needed, I will advise using Nagios Core on CentOS.

Nagios Core on CentOS is a good product and has enterprise support, so I believe it is a solid and reliable monitoring tool. However, it belongs more to the traditional infrastructure monitoring world than to modern cloud-native observability. I believe Nagios is working on that, so in the future, it will support hybrid cloud-native applications as well. I give this review a rating of ten out of ten.

My main use case for Nagios Core on CentOS is for monitoring purposes, primarily infrastructure and application servers. I rely on it most for managing and deploying our application servers, some applications, and storage.

In my environment, Nagios Core on CentOS is set up to monitor web services and infrastructure level. If anything goes down, Nagios Core notifies me via mail for the server, the particular service, and anything at the infrastructure level, so I receive notification and we fix the issue as soon as possible according to the priority level.

We are moving forward from Nagios Core to an agent AI, and we are thinking about how to integrate Nagios Core with AI and monitor all aspects to easily manage everything.

Nagios Core on CentOS has positively impacted my organization because if there is any issue from the infrastructure side or application-wise, it automatically sends me a notification if something goes down, allowing us to easily and quickly solve the issue as soon as possible. This makes it a good option with multiple alerts available through mobile alerts, mail, and Slack messaging tools.

Since using Nagios Core on CentOS, I have noticed specific improvements in downtime and how quickly my team can respond to issues. Previously, without Nagios Core, we were digging into issues to find the root cause. Now when I install and configure Nagios Core, all the prerequisites are defined in the configuration, so if anything goes down, such as services that need to be monitored and examined all the time, I just need to configure it accordingly. If it goes down, it automatically sends a notification for these services, particularly if memory or disk space goes down, and we check the logs and fix it accordingly, which has led to a very significant improvement in downtime.

The best feature of Nagios Core on CentOS is that it is open source with many plugins available for installation and monitoring. If any application server or service goes down, we can take care of it very easily and configure it accordingly.

Plugins have helped my team significantly, particularly the database MySQL plugin and numerous other plugins for SVN and other applications.

Nagios Core on CentOS has positively impacted my organization because if there is any issue from the infrastructure side or application-wise, it automatically sends me a notification if something goes down, allowing us to easily and quickly solve the issue as soon as possible. This makes it a good option with multiple alerts available through mobile alerts, mail, and Slack messaging tools.

Since using Nagios Core on CentOS, I have noticed specific improvements in downtime and how quickly my team can respond to issues. Previously, without Nagios Core, we were digging into issues to find the root cause. Now when I install and configure Nagios Core, all the prerequisites are defined in the configuration, so if anything goes down, such as services that need to be monitored and examined all the time, I just need to configure it accordingly. If it goes down, it automatically sends a notification for these services, particularly if memory or disk space goes down, and we check the logs and fix it accordingly, which has led to a very significant improvement in downtime.

Nagios Core on CentOS can be improved by making it easier.

Specifically, I would prefer the configuration and interface of Nagios Core on CentOS to be easier, more easily configured, and have an easy UI-based way to monitor all aspects.

I would add that it needs to improve in several areas, for example, if the UI were changed to show the interface in a GUI that is metric-based. There are many things that need improvement in my opinion, especially if the UI needs to be changed.

I have been using Nagios Core on CentOS for around five years and CentOS for around ten years.

In my experience, Nagios Core on CentOS is stable, and there are no issues.

Nagios Core on CentOS scalability is easy, making it simple to scale up as my organization grows and needs to monitor more servers or services.

Before using Nagios Core on CentOS, I do not particularly remember which tool I was using previously, but I found it easy to configure Nagios according to my needs in my environment.

I chose a rating of eight out of ten because some things need to be improved at the UI level, and there are some configuration areas that I do not recall at this time, but the UI-based components and some configuration parts need improvement.

Since using Nagios Core on CentOS, I have seen a return on investment, specifically in the form of money saved and time-saving.

I have not been involved in the pricing aspect of Nagios Core on CentOS because another team handles the pricing and related matters.

Before choosing Nagios Core on CentOS, I evaluated other options including Prometheus.

My advice for others looking into using Nagios Core on CentOS is that it is easy to configure and manage services at the infrastructure level, including all infrastructure in Windows, Linux, and macOS, effectively capturing all logs and metrics and monitoring the services that are required, which can be set up accordingly. I would rate this solution an eight out of ten.

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.

Nagios Core on CentOS is used to monitor different services for Windows servers and Linux servers, including monitoring services for MySQL databases and Bugzilla servers, among many others. In a recent scenario, I used Nagios Core on CentOS while working on many web projects, including website development, where I utilized the URL monitoring feature to monitor the response code and verify whether I was receiving a response 200.

Using the 200 response code, I monitored different website links to ensure my website was working properly and receiving quick alerts.

Nagios Core on CentOS has positively impacted my organization because it is an open-source tool that has been very useful in monitoring different services using both custom plugins and the default plugins it provides. This gives me quick alerts to monitor various services and allows me to resolve issues quickly when any service goes down.

The feature I appreciate most about Nagios Core on CentOS is that I can customize the plugins and use them to monitor the services required by me, which are not provided by default in some monitoring tools. This allows me to monitor using custom plugins.

The best features Nagios Core on CentOS offers are the capabilities to monitor both Windows and Linux services, as well as the ability to write custom plugins to monitor different services if the needed plugins are not provided by default.

I worked for MakeMyTrip India Private Limited where I created custom plugins for Nagios Core on CentOS, including plugins for monitoring different website bookings. If bookings were less than 2,000 in an hour, I was able to monitor that using Nagios Core on CentOS.

To improve Nagios Core on CentOS, I believe that many more plugins could be generated by the Nagios organization, such as those for monitoring services of an F5 load balancer or different other hardware devices such as Imperva WAF. Having those plugins would be very useful.

I have been using Nagios Core on CentOS for the last 16 years, first using it in 2010.

The advice I would give to others looking into using Nagios Core on CentOS is that it is a very useful monitoring tool that provides quick monitoring alerts, and the plugins can be customized as needed, making it very useful. I give this product a rating of 10.

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 to monitor remote servers and configure alerting. I use default plugins available in NRPE to monitor Linux instances and other running services. I created custom plugins to monitor Docker containers and the processes running inside them, all monitored through Nagios.

The way I set up Nagios Core on CentOS is unique because I monitor Docker containers at a granular level. If any processes, such as Python microservices, exit, I receive alerting to Google Chat and email. A separate team works with me to continuously monitor for alerts and inform respective team members to quickly investigate and resolve problems.

The best features of Nagios Core on CentOS are complete infrastructure monitoring and real-time alerting and notifications. The plugin-based architecture allows me to create custom plugins, and the centralized dashboard provides comprehensive visibility. Nagios Core on CentOS has positively impacted my organization by significantly reducing downtime through timely alerts configured according to my specifications. It has provided centralized visibility across all infrastructure. I monitor many instances using Nagios and find it highly customizable for my use case.

Nagios Core on CentOS could be improved with an official Docker image from Nagios Core. Currently, I created my own Docker image and use it by mapping volumes to the Linux host. Having an official Docker image with a compose file or the ability to deploy into a Kubernetes environment would be beneficial.

I would like to add feedback regarding the interface. If the interface could be made more similar to Grafana for checking historical data, that would be valuable. I already have the data available but must view it in log form. Making it more similar to Grafana would be helpful, though I understand this requires consideration from a product perspective. Overall, the solution looks good to me.

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

In my experience, Nagios Core on CentOS is very stable and continues to function well.

Regarding Nagios Core on CentOS's scalability, it is currently running on a single instance. I do not need to scale it extensively, and it runs stably in its current configuration.

I have not needed to contact customer support, but I hope the service is good.

Before switching to Nagios Core on CentOS, I used a different solution to obtain more aggressive alerting for custom services.

Nagios Core on CentOS is deployed in my organization in a public cloud rather than directly on a host. It is deployed using a Docker image and containers in a dockerized environment. My experience with the open-source version was straightforward, and deploying it through a Docker image made the process easier. I created a custom Docker image that helps new team members deploy Nagios Core on CentOS in different environments.

A separate team works with me on Nagios Core on CentOS implementation. We continuously monitor for alerts, and when an alert occurs, the team informs respective team members to quickly investigate and resolve the problem.

I have seen a return on investment in terms of saving time. Any downtime or service failure results in time savings. Regarding specific outcomes or metrics on reduced downtime, before monitoring was fully in place, issues were often detected late. With proactive alerts, unplanned downtime dropped by around thirty to forty percent.

Regarding pricing, setup cost, and licensing, I used the open-source version, so the setup cost is zero and no license is required. This made it easy for me to deploy Nagios Core on CentOS.

Before choosing Nagios Core on CentOS, I evaluated other options including Grafana, but later switched to Nagios Core on CentOS.

My advice to others looking into using Nagios Core on CentOS is to definitely go for it. It is very good and I appreciate the alerting mechanism. I provide this review with an overall rating of eight out of ten.

My main use case for Nagios Core on CentOS is due to the enterprise platforms we run that are based solely on open source; for our R&D division, we need to use CentOS. Wherever we are using CentOS and Ubuntu, we are using Nagios Core on CentOS for monitoring.

I monitor all our server devices as a server and storage administrator through Nagios Core on CentOS, especially for server administration; all hardware level monitoring and OS level monitoring will be pushed into Nagios Core on CentOS, where we want to see the CPU memory usage or network usage.

In terms of my main use case with Nagios Core on CentOS, when we run any high load or high workload usage, Nagios Core on CentOS will be very helpful because we can check the current load usage of the system, processes running, causing bottlenecks, and network usage.

The best features Nagios Core on CentOS offers include systems usage, specifically the load average, and while the CPU and memory usage graphs are not displayed in a granular way, they are useful for analyzing trends and history, and I can create host groups for monitoring to check the entire cluster's usage.

Host group monitoring helps me in my daily work because we have a lot of divisions, so we cannot add all the hosts into a single group; we create host groups to segregate based on R&D, production, testing platform, and development platform.

Regarding features, I have tried the application monitoring feature, which is not that great but still useful; for open source, it is very helpful, though there are improvement areas in the application side. For server monitoring, especially, it is very good, while a few things are lagging in storage.

Nagios Core on CentOS has positively impacted my organization by being very helpful budget-wise, as we rely on open source due to budget constraints for each division.

I believe Nagios Core on CentOS can be improved mainly by the granularity of the metrics; while most enterprise metrics are available, some complex ones are missing, and it would be beneficial to integrate more APIs for better data granularity, which newer users struggle to see.

Regarding needed improvements, at this stage it is better, and I do not think any new things are required.

I have been using Nagios Core on CentOS for around seven to eight years.

Nagios Core on CentOS is stable.

Currently, we have not integrated Nagios Core on CentOS with other tools; it is a separate platform, and while we use other monitoring tools, there have been no integrations.

The customer support for Nagios Core on CentOS is almost equal to that of enterprise solutions.

Previously, we used ManageEngine, which was not that great, prompting our switch to Nagios Core on CentOS for its open source nature and similar features without additional costs.

I faced no major challenges during the setup or use of Nagios Core on CentOS, aside from low-level users struggling during installation; we created knowledge base articles to assist, so now we are not facing issues, although there was some initial struggle.

We handle alerting and notifications with Nagios Core on CentOS by enabling notifications to email IDs, triggering alerts to our separate monitoring NOC team that checks emails and diverts alerts to the respective team.

For Nagios Core on CentOS, we manage configuration and updates manually, but we are planning for automation.

We ensure security and access control for Nagios Core on CentOS by fixing all security vulnerabilities on time; our Linux admin team continuously monitors Linux devices, including Nagios Core on CentOS servers, and addresses any software level vulnerabilities.

I estimate cost savings of almost fifty thousand dollars per year thanks to using Nagios Core on CentOS.

The main factors that influenced my decision to choose Nagios Core on CentOS over other monitoring solutions are mainly its free of cost, open source nature, which saves a lot of money, and it being easy to install, so even junior staff can set it up straight away to start monitoring.

Before choosing Nagios Core on CentOS, we evaluated other options, including VMware's vROps and Prometheus with Grafana, but Nagios Core on CentOS received positive feedback for being user-friendly and widely used, which led us to select it.

My advice for others considering Nagios Core on CentOS is to focus on cost savings since organizations globally are cutting costs.

My additional thoughts on Nagios Core on CentOS include that certain metrics could be improved or added; however, ninety percent of them are already available. I would rate this product an eight out of ten.

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.