Icinga vs. PingPlotter

Icinga is a world-class monitoring system. It can be used for most general monitoring situations. It is not a silver bullet, however, and there are instances where domain-specific monitoring systems are necessary. However, the output from those monitoring systems can be funneled into Icinga as a central monitoring and alerting system.

Incentivized

It is well suited for performing monitoring and testing from a single device. It is less appropriate if you have to monitor from multiple different endpoints. That type of deployment would be more of an enterprise application. If you are looking for an end user monitoring solution then PingPlotter is the one for you.

Incentivized

• Wealth of community-developed plugins.
• Stable codebase.
• Icinga 2 supports distributed monitoring.
• Very performant, can support tens of thousands of checks per server.

Incentivized

• Monitor traffic in network
• Measure stops when contacting network locations such as websites
• Measures the lag and latency it takes to contact network locations
• Gives you both induvidual measurements as well as good oversight
• identifies when network lag or disconnect occurs

• 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.

Incentivized

• Its a little confusing to see which targets are currently running pings and which ones are displayed in the plots.
• Starting and stopping pings requires a right click and that would be better with a play/pause button I think.
• Ability to drag and drop the graphs to reorder them.
• more columns to show which targets are running and which are displayed. Currently this is done with symbols so you cant sort by just the running targets for example I've found.

Incentivized

Icinga is a solid solution which does everything it promises. It is backwards compatible with most Nagios instances, making the transition very easy. Once you get the hang of installing new plugins and editing configuration files expanding its monitoring capabilities are easy.

Incentivized

I have not had much contact with the PingPlotter support, only one time have I went to them and it was a positive experience. The questions I had were answered quickly and professionally. I have no issue with the experience I had with the Support team. This was from before and after the purchase of the product.

Incentivized

Icinga is better than Nagios because of its nicer user interface. New Relic can monitor CPU/memory and disk usage, but it's more of a performance and application troubleshooting tool rather than monitoring

Incentivized

A balance of a generic tool vs a network equipment product is necessary when investigating network incidents or disruptions. Need to train the engineer to use both tools to perform their analysis and to dive down to the issues as fast as they can. Experience with the tools will continue to play a part if we were to adopt PingPlotter

Incentivized

• With one check you know which applications are faulty e.g. after an upgrade. Which is big time saver
• You easily detect outages ion the applications so that your customer ideally does not even realize there was an outage.
• Detect if the environment does deliver the same result as in the same time as before to detect shortages.
• Additional information when debugging. Saved us several hours where we could simply point to a database which was slow.

Incentivized

• Great ROI, troubleshooting time has been reduced by 90%
• Network Discoveries used to take 2 to 3 hours and were inconsistent - now it is a matter of minutes
• lacks integration into our MSP toolkit, and we now use it as a stand alone product

Incentivized