Dave advises setting benchmark goals for any environment in your hybrid cloud architecture. These criteria include things like: cost, technology, license management, support capabilities, data security, application longevity, performance, and internal/external interfaces, Newell says.
Initial evaluations of a particular vendor or of a workload’s fit for a particular environment are important, of course. Newell also advises using metrics or KPIs across any environment in your hybrid cloud on a continuous basis. The aforementioned example of increasing outages or downtime (that doesn’t have a ready explanation) is a fundamental one, but there are others. These become your own built-in early warning system that things might not be going according to the plan, and you can then act accordingly.
“Your hybrid cloud objectives need to be realigned when service level agreement (SLA) failures begin to increase, escalations begin to consume more management involvement, unplanned technology refreshes impact your cost models, training requirements significantly increase for your IT resources, or security controls fail to meet your business expectations,” Newell says.
Read the full article on The Enterprisers Project