Overview

Product video
This is a repackaged open source software wherein additional charges apply for extended support with a 24 hour response time.
Nagios Core 4.5.9 on CentOS 10 provides a powerful monitoring solution for IT infrastructure. This AMI is designed to help system administrators and DevOps professionals efficiently monitor servers, network devices, and applications to ensure uptime and performance.
Key Features:
- Comprehensive Monitoring: Track the status of hosts, services, and applications in real-time, enabling proactive management.
- Alerts and Notifications: Receive instant alerts via email or SMS on system issues, allowing for quick resolution and minimal downtime.
- Flexible Configuration: Easily configure monitoring parameters and plugins tailored to specific environments or applications.
- Web-Based Interface: Access the user-friendly web interface to visualize monitoring data, manage devices, and configure alerts with ease.
Benefits:
- Enhanced Reliability: By continuously monitoring your IT infrastructure, you can detect potential issues before they lead to outages.
- Customizable Reporting: Generate detailed reports to analyze system performance and availability over time, aiding in capacity planning and optimization.
- Community and Professional Support: Leverage the extensive community support for troubleshooting or choose extended support options for timely assistance.
Use Cases:
- Data Center Monitoring: Maintain visibility into your data center operations, ensuring all systems and services are running optimally.
- Cloud Resource Management: Keep track of resource utilization and performance in your cloud environment, leading to better resource allocation and cost management.
- Application Performance Monitoring: Monitor critical applications to ensure they are performing as expected and delivering services without interruption.
Deploy Nagios Core 4.5.9 on CentOS 10 in your EC2 environment to empower your IT monitoring capabilities with a robust and reliable solution.
Try our most popular AMIs on AWS EC2
- Ubuntu 24.04 AMI on AWS EC2
- Ubuntu 22.04 AMI on AWS EC2
- Ubuntu 20.04 AMI on AWS EC2
- Ubuntu 18.04 AMI on AWS EC2
- CentOS 10 AMI on AWS EC2
- CentOS 9 AMI on AWS EC2
- CentOS 8 AMI on AWS EC2
- Debian 12 AMI on AWS EC2
- Debian 11 AMI on AWS EC2
- Debian 10 AMI on AWS EC2
- Debian 9 AMI on AWS EC2
- Red Hat Enterprise Linux 9 (RHEL 9) AMI on AWS EC2
- Red Hat Enterprise Linux 8 (RHEL 8) AMI on AWS EC2
- Red Hat Enterprise Linux 7 (RHEL 7) AMI on AWS EC2
- Oracle Linux 9 AMI on AWS EC2
- Oracle Linux 8 AMI on AWS EC2
- Oracle Linux 7 AMI on AWS EC2
- Amazon Linux 2023 AMI on AWS EC2
- Windows 2022 Server AMI on AWS EC2
- Windows 2019 Server AMI on AWS EC2
- Docker on Ubuntu 22 AMI on AWS EC2
- Docker on CentOS 10 AMI on AWS EC2
Highlights
- Comprehensive Monitoring Capabilities: Nagios Core 4.5.9 on CentOS 10 offers robust monitoring solutions for servers, networks, and applications. With its extensive plugin architecture, users can customize checks to monitor various metrics, ensuring optimal performance across systems. The intuitive web interface allows for easy visualization of monitoring data, enabling quick identification and resolution of issues, resulting in improved uptime and system reliability.
- Scalability and Flexibility: This AMI is designed to scale effortlessly, accommodating small to enterprise-level environments. Users can deploy multiple instances across different geographical locations for enhanced redundancy and load balancing. The flexibility of CentOS allows seamless integration with existing infrastructures and tools, making it the ideal choice for organizations looking to implement a centralized monitoring solution without compromising on performance.
- Alerts and Notifications: With Nagios Core's advanced alerting system, users can receive timely notifications of issues, which facilitates proactive management of IT resources. The tool supports various notification methods including email and SMS, ensuring that stakeholders are informed of critical events as they occur. The customizable alert thresholds empower teams to prioritize issues effectively, ultimately leading to faster resolution times and reduced operational downtime.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
t3a.micro Recommended | $0.07 |
t3.micro | $0.07 |
t2.micro | $0.21 |
m5a.12xlarge | $3.36 |
g4ad.4xlarge | $1.12 |
m7a.32xlarge | $4.48 |
g3.8xlarge | $2.24 |
x1e.8xlarge | $2.24 |
c5d.2xlarge | $0.56 |
r6a.16xlarge | $4.48 |
Vendor refund policy
The instance can be terminated at anytime to stop incurring charges
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
System Update
Additional details
Usage instructions
Once the instance is running, connect to it using a Secure Shell (SSH) client with the configured SSH key. The default username is 'ec2-user'.
OS commands via SSH: SSH as user 'ec2-user' to the running instance and use sudo to run commands requiring root access.
User interface: http://nagios/ Username: nagiosadmin Password: (instance-id of the launched instance)
Nagios config location /usr/local/nagios/etc/nagios.cfg
Verify nagios configuration: /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Add additional login users with the following command: htpasswd /usr/local/nagios/etc/htpasswd.users <USERNAME>
Resources
Support
Vendor support
Email support for this AMI is available through the following: https://supportedimages.com/support/ OR support@supportedimages.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Monitoring has reduced downtime and now optimizes alerts and automated off‑hours responses
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I have never used the CentOS support for Nagios Core on CentOS technical support.
Which solution did I use previously and why did I switch?
Which other solutions did I evaluate?
I evaluated PRTG before choosing Nagios Core on CentOS, but it's so expensive.
What other advice do I have?
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.
Reliable alerts have protected critical environments but documentation still needs improvement
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Nagios Core on CentOS for about five years.
What do I think about the stability of the solution?
In my experience, Nagios Core on CentOS is quite stable.
What do I think about the scalability of the solution?
I already have many endpoints, but I don't need any scalability because the number of my endpoints is fixed and not increasing.
How are customer service and support?
I have never needed to reach out to customer support for Nagios Core on CentOS.
Which solution did I use previously and why did I switch?
Nagios Core on CentOS is the first monitoring tool I have installed.
How was the initial setup?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My company is using the open-source version of Nagios Core on CentOS, so there were no pricing, installation, or licensing costs.
Which other solutions did I evaluate?
I evaluated Zabbix and also installed it, so I am using multiple monitoring tools: Nagios Core on CentOS and Zabbix.
What other advice do I have?
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.
Proactive monitoring has transformed incident response and now reduces downtime significantly
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
It has been two years that I have been using Nagios Core on CentOS.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
What other advice do I have?
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.
Monitoring has reduced outages and improves proactive issue resolution across our infrastructure
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Proactive alerts have reduced downtime and improve response to infrastructure issues
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Nagios Core on CentOS for around five years and CentOS for around ten years.
What do I think about the stability of the solution?
In my experience, Nagios Core on CentOS is stable, and there are no issues.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
Since using Nagios Core on CentOS, I have seen a return on investment, specifically in the form of money saved and time-saving.
What's my experience with pricing, setup cost, and licensing?
I have not been involved in the pricing aspect of Nagios Core on CentOS because another team handles the pricing and related matters.
Which other solutions did I evaluate?
Before choosing Nagios Core on CentOS, I evaluated other options including Prometheus.
What other advice do I have?
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.