9 Reasons not to Install Nagios in your Company
Nine key reasons to avoid using Nagios in your IT infraestructure. It is based on technical and business aspects. |
|
|
Comments (5)
just gearing up to install nagios for a customer myself, the points for each install being different, limited out of the box (most certainly not on debian, which comes prepackaged with hundreds of plugins), difficult to integrate with automatic provisioning (it appears someone already did the work at least for saltstack, because my server was provisioned quite automaticly), i can easily refute. and most of the rest are, as you say, anti FOSS PR nonsense.
seems to be their style, they even downtalk their own community version.
greetings, eMBee.
greetings, eMBee.
The same thing was true for the pandorafms site the last time I tried it.
I'm not going to globally allow scripts to get a page to load without a good reason.
What a crock. I haven't read this much FUD in a long, long time. I wondered where all the former anti-OpenSource folks went.
I read through each numbered point and instantly recalled a similar argument from 10-15 years ago why you shouldn't, say, allow Linux to be installed within your company: No roadmap.. You need a dedicated admin (who'll, presumably, actually want to be paid for their work. The horror!)... etc.. I particularly liked the "bespoke" installation problem. Because, you know, all companies' IT setups are identical so your monitoring "solution" should be, too. (I suppose the argument is that "bespoke" == "needs dedicated and allegedly expensive admin".)
Are there still people who have been in IT management for more than a handful of years who would find these points convincing?
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Sign up and post (it is free) or Log in and post
