2 of them are not available in nagios at all (graphing and anomaly detection) and 1 already sucks completely (UI), so I'm not sure this is a good way to look at the presentation.
It isn't very clear to me which Nagios plug-ins are considered standard, and perhaps that sort of confusion is what creates all the FUD surrounding Nagios.
When two of the six points don't have answers, and one of those has "I will have to write something", it's pretty clear that the talk is not 'stop using Nagios right now', but 'what do we need to replace Nagios and do it right'. It's not a talk about a tool that is ready now.
Would you mind to elaborate on your problems with Zabbix?
We use it for a small ISP since nearly two years and are quite happy with it. All limitations that came up during integration could be fixed by writing some small scripts.
Even upgrades worked.. :)
So if you have any Zabbix pain that might be waiting for us, please share.
Can it be completely driven by some configuration management tool and run without persistent storage? These are two parts of nagios that make it work for me. Granted, I didn't look too far, but some basic research says you need a database and have to manage everything via GUI.
Shinken was written by Jean Gabès as a proof of concept for a new Nagios architecture. Believing the new implementation was faster and more flexible than the old C code, he proposed it as the new development branch of Nagios 4.[3] This proposal was turned down by the Nagios authors, so Shinken became an independent network monitoring software application compatible with Nagios
