Skip to main content

Instance Monitoring

vCloud Monitoring provides real-time performance charts for virtual machines, tracking CPU, RAM, disk IOPS, and network traffic to help optimize resource usage and detect issues early.

Access Monitoring

  1. Log into vCloud system
  2. Navigate to instance details page
  3. Select Monitoring tab

Performance Metrics

Monitoring displays real-time charts for four key metrics:

Figure needed: Overview of monitoring dashboard showing CPU, RAM, disk IOPS, and network utilization charts Figure needed: Detailed CPU usage chart with percentage over time Figure needed: Memory usage chart showing consumption in MB

CPU Usage

Metric: CPU usage percentage (%) Purpose: Shows CPU utilization against allocated resources

Key Indicators:

  • High peaks indicate heavy load periods
  • Sustained >80% usage suggests need for upgrade
  • Brief spikes are normal; prolonged high usage indicates issues

Memory Usage

Metric: Physical memory consumption (MB) Purpose: Tracks RAM usage by virtual machine

Key Indicators:

  • Stable usage indicates normal operation
  • Continuous increase without decrease suggests memory leaks
  • Near-limit usage requires upgrade to prevent swap/paging

Disk IOPS

Metrics:

  • Disk Read IOPS: Read operations per second
  • Disk Write IOPS: Write operations per second

Key Indicators:

  • High IOPS indicates intensive disk activity (backups, databases)
  • Sustained high IOPS may require High IOPS disk upgrade
  • Periodic spikes typically relate to automated processes

Network Utilization

Metrics:

  • Receive rates (download) – Kbps
  • Transmit rates (upload) – Kbps

Key Indicators:

  • Sudden high bandwidth may indicate file transfers, backups, or downloads
  • Sustained high upload suggests web/API service traffic
  • Unusual traffic patterns may indicate network attacks

Best Practices

Performance Optimization:

  • Monitor trends over time, not just current values
  • Set up alerts for sustained high usage (>80% CPU/RAM)
  • Plan capacity upgrades before reaching resource limits
  • Investigate sudden changes in patterns

Troubleshooting:

  • Combine monitoring data with system logs for comprehensive analysis
  • Check for correlations between different metrics
  • Monitor during peak and off-peak hours
  • Document baseline performance for comparison
Recommendation

Combine monitoring data with system logs for comprehensive performance analysis and issue root cause identification.