Cloudops tools: More is not better

Cloud operations, or cloudops, is becoming the problem to solve as enterprises operationalize their cloud and multicloud deployments. The ideal pattern of management involves a pragmatic approach to operations by leveraging tools to automate predetermined procedures and runbooks. Right now, many overwhelmed managers toss cloudops tools at the problems and hope for the best.

The issue is one of balance. To put cloudops solutions and tools to their best uses, you need to define why and what before you determine how. It’s not that the tools are unimportant; rather, the tools should meet specific requirements, such as performance, security, cost management, governance, automation, and self-healing.

The operational aspects of cloud computing are the highest-priority concepts in my mind. Almost all other components of cloud computing have dependencies into cloudops.

For example, security breaches can be spotted by process saturation monitoring from an AIops tool. I’ve defended against breach attempts in the past. The first indications came from cloudops tools, not from security systems.

The focus needs to be on the optimal suite of cloudops tools that will best meet the optimal requirements. I’ve been calling this a “minimal viable cloudops toolset,” or MVCOT. The ideal MVCOT is a streamlined collection of tools that are optimized for the cloud and noncloud systems under management.

How do you find this MVCOT nirvana? I would suggest the following:

Copyright © 2020 IDG Communications, Inc.

Source link