|
Costs Comparison |
|
|
BMC Performance Manager For Servers vs. Monitoring Studio Since the PATROL Agent, part of BMC Performance Manager for Servers, is a requirement in order to install and use Monitoring Studio KM for PATROL, Monitoring Studio represents an additional cost of license. Any organization that is considering the monitoring of a custom application of any IT component for which no out-of-the-box monitoring solution already exist will have to evaluate the following equation:
Whenever this equation is true, the purchase of Monitoring Studio actually turns out to be an economically viable. The biggest problem relies in the evaluation of the cost of a given application failure as well as its probability (in a 3-year period for example). Monitoring Studio vs. Development of a Custom solution As it has already been shown by many studies, the development cost of any software solution is an exponential function of the difficulty involved, multiplied by the number of features required and augmented by the time needed for the packaging and development. This does not even take into account the time involved in getting a developer skilled enough in the specific domain of PATROL, PSL and general monitoring understandings.
What this somewhat intimidating equation shows is, that there are many factors that can dramatically increase the cost of a custom development, and some of these factors are rather hard to predict. The most costly factor in this equation though is the number of features and their difficulty to implement. The typical scenario implies that an organization having chosen to develop a custom KM to monitor a custom application already considered the monitoring through features provided by BPM for Servers. Having decided to go for custom development means that the features in BPM for Servers were not advanced enough to serve the multiple and/or complex monitoring needs of the organization. In order to illustrate the development costs of some examples of commonly used monitoring features, the table below shows how long it took to highly trained, experienced PATROL developers at Sentry Software to integrate these features in Monitoring Studio. The numbers below must certainly be multiplied by a factor of 1.5, two or even more if the development is made by a person less experienced than the developers at Sentry Software.
Experience shows that a typical custom KM development project involves an incompressible period of 25 days followed by a recurring period of tests, validations and qualification depending on the quality of the development made. This number of typical 25 days also means that custom KMs often drop most interesting features because they cost too much to implement and never fit in the budget. Typically, no custom KM will ever be able to correctly deal with JMX-instrumented Java applications because it is difficult to implement, involves different technologies and great deal of testing on different platforms. The next table summarizes the typical steps to produce a valid monitoring solution for a custom application and compares how long it takes from the specifications stage to deployment into production. Time Taken to Produce a Valid Monitoring Solution
The comparison gets even worse if the specifications are not taken into account and costs of support, maintenance and new features are added to the total. As explained before, developing a custom monitoring solution allows for the greatest flexibility but this flexibility has a great cost, not just from a pure price point of view, but from a planning point of view. While a BMC PATROL administrator team can respond in less than 3 days to product a valid monitoring solution once it has received the specifications when they use Monitoring Studio, it would take them more than 40 days to do it from scratch! Conclusion Faced with a frequently occurring situation PATROL administrators need to find a monitoring solution for applications/devices/technologies not covered by their regular tools, they have to make a choice between three solutions:
The picture below recapitulates the comparison of each solution from both a feature and costs point of view.
It appears, there are only two cases where it is not recommended to purchase, install and use Monitoring Studio KM for PATROL to setup the monitoring of a custom application or an IT component for which there is no KM that already exists: 1. The organization has only applications that produce fairly simple log files. The monitoring of all past, current and future applications can be done with log files analysis and process monitoring. 2. An application has complicated monitoring needs not covered by Monitoring Studio and the organization is ready to invest enough time and expertise in order to create the “perfect” customized monitoring solution. As a matter of fact, most organizations that have tried the Monitoring Studio KM are now phasing out their existing custom KMs with Monitoring Studio because they realize that the cost of Monitoring Studio is even less than just the cost of the maintenance of the custom KMs. According to current users, BMC Performance Manager Monitoring Studio turns out be an ideal way to maximize the monitoring coverage of custom applications. Credits This study has been completed with the valuable contribution of current Monitoring Studio customers, BMC Software consultants, and Sentry Software developers. For more information, please contact your BMC Software consultant or Sentry Software at sales@sentrysoftware.com. About Sentry Software™ Sentry Software is the developer of the software product licensed under the name BMC Performance Manager Monitoring Studio. This licensed product allows usage of two technologically different solutions of the same product:
|