Filter Ratings and Reviews
Filter 17 vetted Icinga reviews and ratings
Reviews (1-5 of 5)
Companies can't remove reviews or game the system. Here's why.
January 30, 2019
Icinga is a world-class monitoring system. I've used this product for several companies, monitoring everything from typical server response to verification that specific daemons are up and running. The client/server nature of Icinga allows for monitoring of nearly anything you can write a script for. Installing the client on a server, you can monitor local CPU, memory, processes, etc. without the need for SNMP. Communication between client and server is TLS encrypted, adding security where typically there is none. We have used Icinga across the entire enterprise to monitor network and system devices.
- Flexible: Monitoring is done via scripts. If you can write a script to return a go/no go response for something you want monitored, then you can monitor it.
- Client/Server Model: The client/server model allows for secure communications between systems. Additionally, it allows data to continue to be collected in the event of a communication problem, queuing the data for upload when communication is restored.
- Simple, but powerful, configuration: The configuration language used by Icinga allows additional flexibility without having to directly specify every relation. That is, you can use commands to apply a given configuration to hosts and services based on common properties.
- Distributed configurations can be somewhat challenging to deploy. However, once set up, a multiple master setup can result in a highly available, resilient monitoring system.
- Icinga supports a centralized configuration system akin to something like svn or git. Understanding how this works and using it in practice can be something of a challenge for beginners.
March 18, 2019
Icinga is our core monitoring platform for all non-Windows systems. However, our Windows group is actively looking to abandon their current platform and implement it for their systems as well.
- The price tag is right. Monitoring systems are only as good as the time you put into them, so why start with a huge buy-in before dumping man hours in also?
- Despite some older styled interfaces, the dashboard is easy to manage and understand.
- Scalability is excellent.
- Icinga is a monitoring solution only. It doesn't generate PHB graphs, but everyone seems to expect it to.
- Configuration can be confusing and difficult. For non-unix people the learning curve is very intimidating.
Icinga was in place when I started, it continues to be used for a legacy environment. It monitors the status and availability of servers and services, previously for the entire production and quality assurance environments and now just for a legacy mail processing system. We chose to move away from Icinga about a year ago.
- Wealth of community-developed plugins.
- Stable codebase.
- Icinga 2 supports distributed monitoring.
- Very performant, can support tens of thousands of checks per server.
- Difficult, arcane configuration.
- Very difficult to integrate into modern configuration management systems.
- Hard to fit concepts like auto-scaling groups of ephemeral servers into Icinga's aging conception of servers as static entities.
Like Nagios, we used Icinga as a network monitoring solution. It provided us with insights as to when a device was not functioning properly or failed completely. It was implemented throughout the entire organization, monitoring all our most critical assets.
- Excellent monitoring solution, once you understand the configuration language adding additional hosts and services is easy.
- Scalable and highly configurable.
- Beautiful web UI.
- Very very nice API.
- High learning curve, setting up Icinga from scratch can be a bit of a challenge starting out.
- If the io2db process fails you UI stops updating, which can be very frustrating.
- There is no simple mechanism for adding new hosts and services through the web UI, it's all very config-file based.
Icinga is one of our internal monitoring user interfaces. It's the front end to Nagios basically. We incorporate it with our Pager-Duty service and will receive pages if critical services go down. Our technical operations team is the primary department that uses Icinga, however more and more of the engineering and development teams are getting logins as they will be given more responsibility in monitoring their deployed services.
- I think Icinga has a great search feature. I can always search for the hosts, host groups, or check names. When using just regular Nagios, I don't recall being able to do this search.
- The fact that I can use Active Directory or LDAP for logins is a great feature.
- If you are familiar with Nagios, it's very simple to combine the two products to get a polished finished product.
- The user interface is good, but I had trouble with the customization of the front end.
- Certain things can be copied and pasted. Certain things can't. I would like to see all things be able to be copied and pasted.
Icinga Scorecard Summary
What is Icinga?
Icinga is a network monitoring platform. The newest version is an open source monitoring system that includes alerts and reporting capabilities and enables community development and support of the platform. Icinga provides automated data import methods from external or preexisting sources.
Icinga’s extended functionality is modularized for efficient licensing. Add-ons include VMware integration, certificate monitoring, and Elasticsearch compatibility for data logging.
Icinga Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |