With some of the research I completed towards the end of last year, I take a pretty consistent set of requests on the evaluation and use of open source monitoring. If you are following some of the fun conversations on “monitoring sucks” you will notice that not only do most traditional monitoring systems fail to deliver any high value in general, but they often fail and do poorly. The reaction that many have had is trying to implement open source to reduce the cost, since it pretty much “sucks” anyway… logic makes sense, but the issue is that Nagios and other related open source tools are often much worse than commercial solutions. Another approach to getting ahead of this problem is looking at monitoring which comes with the purchased technology stack (Microsoft, Oracle, VMware, SAP, and others). An alternate way is to investigate the many lower cost and free monitoring tools on the market. These companies often sell significantly less expensive tools which have 80% of the functionality for much lower costs. They often have freeware versions or limited versions. I have put together some discussion on this point along with some insight into many of the solutions on the market.
Solutions covered in this research covers traditionally deployed solutions including : Ipswitch, ManageEngine, Solarwinds, Correlsense, Groundwork, Jinspired, Net Optics, OP5, Paessler, Spiceworks, Splunk, VMTurbo, VMware, Zabbix, and VMTurbo
We also cover those free and low cost tools deployed via monitoring as a service (SaaS) including AppFirst, Boundary, Datadog, GFI Monitis, New Relic, ScaleXtreme.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.