In Beware of the Franken-Monitor, we explained how many enterprises ended up with Franken-Monitors and the dangers associated with assuming that the present state of management tools can make the transition into the software-defined data center (SDDC) and the cloud. In Getting Rid of Your Franken-Monitor, we explained how to use green-field islands to put in place new ecosystem-based management stacks with the intent of eventually retiring your legacy management stacks. In this post, we detail how one could deploy one example of such an ecosystem of tools based upon Splunk and the vendors that comprise its ecosystem.
Articles Tagged with Franken-Monitor
In “Beware of the Franken-Monitor,” we outlined why systems management frameworks have become Franken-Monitors and the dangers of building your own Franken-Monitor. Unfortunately, the reality for most enterprises is that they have probably done some combination of the two. They have bought a framework that became a Franken-Monitor because the vendor of the framework never integrated its acquired components. And then they layered more “Frankeness” on top of their framework by buying, in some cases, hundreds of point monitoring solutions, none of which are integrated with each other or the frameworks.
Ten years ago, legacy management software vendors were busy building Franken-Monitors. Those Franken-Monitors now consist of legacy management offerings that are neither well integrated, nor in any way able to keep up with pace of innovation in the industry. In order to survive your transition to the software-defined data center and the cloud, you will need a management software strategy and a management software architecture that will allow you to keep up with the pace of change without buying or building a Franken-Monitor.