Icinga聽vs聽Nagios

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Icinga
Icinga

51
10
+ 1
0
Nagios
Nagios

577
403
+ 1
94
Add tool

Icinga vs Nagios: What are the differences?

Developers describe Icinga as "A resilient, open source monitoring system". It monitors availability and performance, gives you simple access to relevant data and raises alerts to keep you in the loop. It was originally created as a fork of the Nagios system monitoring application. On the other hand, Nagios is detailed as "Complete monitoring and alerting for servers, switches, applications, and services". Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.

Icinga and Nagios belong to "Monitoring Tools" category of the tech stack.

Nagios is an open source tool with 60 GitHub stars and 36 GitHub forks. Here's a link to Nagios's open source repository on GitHub.

- No public GitHub repository available -

What is Icinga?

It monitors availability and performance, gives you simple access to relevant data and raises alerts to keep you in the loop. It was originally created as a fork of the Nagios system monitoring application.

What is Nagios?

Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Icinga?
Why do developers choose Nagios?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
        Be the first to leave a con
        What companies use Icinga?
        What companies use Nagios?

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with Icinga?
        What tools integrate with Nagios?

        Sign up to get full access to all the tool integrationsMake informed product decisions

        What are some alternatives to Icinga and Nagios?
        Sensu
        Sensu is the future-proof solution for multi-cloud monitoring at scale. The Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments.
        Shinken
        Shinken's main goal is to give users a flexible architecture for their monitoring system that is designed to scale to large environments. Shinken is backwards-compatible with the Nagios configuration standard and plugins. It works on any operating system and architecture that supports Python, which includes Windows, GNU/Linux and FreeBSD.
        Zabbix
        Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.
        PRTG
        It can monitor and classify system conditions like bandwidth usage or uptime and collect statistics from miscellaneous hosts as switches, routers, servers and other devices and applications.
        Kibana
        Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.
        See all alternatives
        Decisions about Icinga and Nagios
        StackShare Editors
        StackShare Editors
        Kibana
        Kibana
        Grafana
        Grafana
        Elasticsearch
        Elasticsearch
        Logstash
        Logstash
        Graphite
        Graphite
        Icinga
        Icinga

        One size definitely doesn鈥檛 fit all when it comes to open source monitoring solutions, and executing generally understood best practices in the context of unique distributed systems presents all sorts of problems. Megan Anctil, a senior engineer on the Technical Operations team at Slack gave a talk at an O鈥橰eilly Velocity Conference sharing pain points and lessons learned at wrangling known technologies such as Icinga, Graphite, Grafana, and the Elastic Stack to best fit the company鈥檚 use cases.

        At the time, Slack used a few well-known monitoring tools since it鈥檚 Technical Operations team wasn鈥檛 large enough to build an in-house solution for all of these. Nor did the team think it鈥檚 sustainable to throw money at the problem, given the volume of information processed and the not-insignificant price and rigidity of many vendor solutions. With thousands of servers across multiple regions and millions of metrics and documents being processed and indexed per second, the team had to figure out how to scale these technologies to fit Slack鈥檚 needs.

        On the backend, they experimented with multiple clusters in both Graphite and ELK, distributed Icinga nodes, and more. At the same time, they鈥檝e tried to build usability into Grafana that reflects the team鈥檚 mental models of the system and have found ways to make alerts from Icinga more insightful and actionable.

        See more
        Conor Myhrvold
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber | 10 upvotes 656.9K views
        atUber TechnologiesUber Technologies
        Prometheus
        Prometheus
        Graphite
        Graphite
        Grafana
        Grafana
        Nagios
        Nagios

        Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

        By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node鈥檚 disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

        To ensure the scalability of Uber鈥檚 metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

        https://eng.uber.com/m3/

        (GitHub : https://github.com/m3db/m3)

        See more
        Interest over time
        Reviews of Icinga and Nagios
        No reviews found
        How developers use Icinga and Nagios
        Avatar of ShadowICT
        ShadowICT uses NagiosNagios

        We use Nagios to monitor our stack and alert us when problems arise. Nagios allows us to monitor every aspect of each of our servers such as running processes, CPU usage, disk usage, and more. This means that as soon as problems arise, we can detect them and call out an engineer to resolve the issues as soon as possible.

        Avatar of Analytical Informatics
        Analytical Informatics uses NagiosNagios

        We use Nagios to monitor customer instances of Bridge and proactively alert us about issues like queue sizes, downed services, errors in logs, etc.

        Avatar of OnlineCity
        OnlineCity uses NagiosNagios

        We use nagios based OpsView to monitor our server farm and keep everything running smoothly.

        Avatar of OnlineCity
        OnlineCity uses IcingaIcinga

        We are running 70+ servers and icinga 2 monitors everything.

        Avatar of Peter Degen-Portnoy
        Peter Degen-Portnoy uses NagiosNagios

        Monitor web servers, databases, utility servers

        Avatar of Veggie Sailor
        Veggie Sailor uses NagiosNagios

        For the monitoring full stack of the platform.

        How much does Icinga cost?
        How much does Nagios cost?
        Pricing unavailable
        Pricing unavailable
        News about Icinga
        More news