- Troubleshooting Not Embedded
- Too Often in Reactive Mode
- No Real-Time Monitoring
- No Central Control
- No Provision for More Than One Hypervisor
- No Preventative Power in the System
- No Workload Placement Optimization
- Automation Is Lacking
- No Cloud Implementation Support
- Limited Channels for Gaining Workload Projection Insight
Troubleshooting Not Embedded
Your system identifies potential performance degradation problems, but leaves the troubleshooting and remediation to you.
Too Often in Reactive Mode
You are consistently in reactive “fire-fighting” mode due to alerts from your monitoring solution notifying you of an anomaly or policy breach.
No Real-Time Monitoring
You know if there was a problem five minutes ago, but you don’t have an up-to-the-second status of your environment.
No Central Control
You have more than one dashboard or you have to drill down several levels to access details regarding the health of your environment.
No Provision for More Than One Hypervisor
You now have a multi-hypervisor environment, but you only have a single-hypervisor workload management system.
No Preventative Power in the System
Your system is intelligent enough to tell you what could happen next, but can’t prevent it from occurring.
No Workload Placement Optimization
Your system makes workload placement decisions based on best “first fit” within a cluster, rather than optimizing placement for the most efficient use of available infrastructure.
Automation Is Lacking
Your system relies on your interpretation of the data collected and your decision making, rather than automatically taking action.
No Cloud Implementation Support
You are building out a cloud and your workload management system doesn’t support cloud implementations.
Limited Channels for Gaining Workload Projection Insight
Your system bases resource projections only on future capacity requirements, rather than workload performance requirements.