Time for ‘the Ugly Truth’. Freeware just isn’t good enough sometimes.
Here’s 5 of the main characteristics of Freeware tools that make them unsuitable for the mid-enterprise:
- Hard to configure out of the box - You want a solution that is intuitive, with a clean interface, that doesn’t require massive amounts of scripting or customization to get started. You definitely wouldn’t want a solution that describes itself as “tricky to configure out of the box – even when you’ve got a good grasp of what’s going on”. Every interface in a good solution should guide you towards the best practices that will save you time and get your project rolling as quickly as possible.
- Extremely cumbersome to maintain and operate – You want a solution that’s well thought out, that doesn’t use conf files to keep lists of devices or massive lists of alerts. You want a system that uses rules, that minimizes the number of full time staff hours to operate, and most of all is easy to learn so that all of your staff can have the ability to work with the monitoring solution.
- Requires massive customization to achieve results – You want a solution that allows you to monitor your infrastructure right out of the box, with a wide variety of available monitoring capabilities for various heterogenous platforms, and that has the ability to monitor all of your common infrastructure stack elements. You definitely don’t want to learn a whole bunch of scripting to do something basic like webservice, ftp, or database monitoring.
- No commercial support – You don’t want to be sifting through knowledgebases, mailing lists, and forums every time you find something that doesn’t seem to make sense when you use a product. You want to be able to pick up the phone, email someone and have experts on the product guide you to a suitable resolution. You need to have this because monitoring is an essential service, the last thing you need is to “wait for someone else who might have had this problem” to reply to your post on a public forum. You definitely don’t want the whole development and support organization to be “one guy”, who “can’t respond to emails directly”. That’s just a supportability nightmare for your selected solution.
- No scaleable architecture – As you continue to grow, all the problems above amplify themselves, but more importantly your infrastructure will grow across disparate geographic locations, and freeware tools just don’t have the kind of distributed archticture as per up.time’s Multi Data Center (MDC) functionality to cope with the needs of multi-site reporting and collection. You need to be able to scale across multiple sites, intelligently and efficiently and manage everything from a single unified console.
The result of the above 5 points is that organizations typically experiment with Freeware tools initially, until they realize that the TCO (Total Cost of Ownership) due to man hours and massive maintenance required to keep their systems going just doesn’t make any sense. This is when the “aha moment” happens and people decide it’s time to graduate to a more robust tool.
Heck, don’t just take it from me, read this stuff directly from the “getting started guide for beginners” from one of the websites of a freeware tool (emphasis added by me). You’ll instantly see all the warning signs that this may not be what you wanted to sign up for.
“Here are some important things to keep in mind for first-time Nag*** users:
- Relax – it’s going to take some time. Don’t expect to be able to get things working exactly the way you want them right off the bat. it’s not that easy.
- Use the quickstart instructions. The quickstart installation guide is designed to get most new users up and running with a basic Nag*** setup fairly quickly. Within 20 minutes you can have Nag*** installed and monitoring your local system. Once that’s complete, you can move on to learning how to configure Nag*** to do more.
- Read the documentation. Nag*** can be tricky to configure when you’ve got a good grasp of what’s going on, and nearly impossible if you don’t. Make sure you read the documentation (particularly the sections on “Configuring Nag***” and “The Basics”). Save the advanced topics for when you’ve got a good understanding of the basics.
- Seek the help of others. If you’ve read the documentation, reviewed the sample config files, and are still having problems, send an email message describing your problems to the nag***-users mailing list. Due to the amount of work that I have to do for this project, I am unable to answer most of the questions that get sent directly to me, so your best source of help is going to be the mailing list. If you’ve done some background reading and you provide a good problem description, odds are that someone will give you some pointers on getting things working properly. “
So you could download a freeware tool and “Relax” because it’s going to “take some time”, or you can download up.time and relax because it’s going to be easier than you thought. The choice is yours.
Don’t worry it’s not like “choose” your own adventure, in the end, whichever way you decide, in the end, up.time always will be the right choice.




