I’ve always been skeptical of those doing capacity planning as the interactions which happen within a typical infrastructure are not only chaotic, but very complex. If you capacity plan within a bubble (network, server, storage, etc) you can look at the discrete component and get a general understanding. If you start to incorporate the private clouds and virtualization we are getting into territory where workloads are moving between infrastructure components without having capacity planning that understands the complex topologies that exist behind each interconnected component. I have been asking capacity planning vendors questions for the last 6 months, and realized no one actually handles these problems, so I teamed up with the capacity management analyst Ian Head (he also covers ITIL and other types of technologies within IT Operations Management) to write about these issues.
You can read more in depth about this topic in our research which was published last night:
I also wanted to point out one of the newest members of our team who is covering BSM and ECA has published his new note which is a vendor landscape of ECA, this is the first vendor specific research we have covered since discontinuing the ECA magic quadrant in 2011.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Mobile Scenario: Taking Mobility to the Next Level
The definition of "mobile" in the post-app era will involve new interactions such as bots and conversations, new devices such as wearables...
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.