v0.7.0

🎯 What's New

1. Multi-Metric Analysis for All 3 Clouds #3

Use --detailed-metrics for comprehensive resource utilization analysis:

Metrics analyzed:

• AWS EC2: CPU, Memory (CloudWatch agent), Network, Disk I/O
• Azure VMs: CPU, Memory, Network, Disk I/O
• GCP Compute: CPU, Memory (monitoring agent), Network, Disk I/O

Confidence-based recommendations:

• 🟢 HIGH — All metrics low, safe to downsize
• 🟡 MEDIUM — Multiple metrics low, review suggested
• 🔴 LOW — Insufficient data, manual verification needed

Usage:

# Default: Fast scan (CPU only)
cloud-cost-cli scan --provider aws --region us-east-1

# Detailed: Multi-metric analysis
cloud-cost-cli scan --provider aws --region us-east-1 --detailed-metrics
cloud-cost-cli scan --provider azure --location eastus --detailed-metrics
cloud-cost-cli scan --provider gcp --region us-central1 --detailed-metrics

2. Fixed JSON Output #4

All logs now go to stderr, allowing clean JSON piping

🙏 Credits

Thanks to @jobi-21 for reporting the issue and suggesting the enhancement.

---

Full Changelog: v0.6.5...v0.7.0