We have a serious issue around capacity management, and what the options are for doing a good job in capacity management. I feel there are the following types of methodologies going in order from fewest to most. Ignore capacity and just fight the fires as they arise. Pros: Easy, no additional work involved. Cons: Unhappy customers, lots of fires, no way to budget for growth or system changes. Treat capacity as a overall metric across unrelated systems, networks, and software. Pros: Gives you a overall idea of the usage of your capacity. Cons: No actionable information, thus you don't actually fix any capacity issues. Treat capacity as alarms, where we get a message and a ticket based on a capacity being passed. Pros: Gives you actionable alarms on capacity problems. Cons: Doesn't give you any priority, or prevent the alarms from being ignored (crying wolf). Treat capacity as reports. Pros: Gives you an idea of what you must take action on. Cons: No idea when you will run out o...
Jonah Kowall is the VP of Market Development and Insights at AppDynamics, driving the company’s product roadmap and vision, entry into new markets and providing technology and business insights. Previously 15 years as a practitioner at several startups and larger enterprises focused on infrastructure and operations, security, and performance engineering. In 2011 Jonah changed careers, moving to Gartner to focus on availability and performance monitoring and IT operations management (ITOM).