The Resource Usage menu in OpsNow FinOps Plus provides a vendor-specific overview of resource data across AWS, Microsoft Azure, and Google Cloud Platform (GCP).
Users can monitor key attributes such as instance specifications, usage status, network details, tags, and billing type — helping identify overprovisioned or idle resources at scale.
✅ Key data fields available
- Resource Type: EC2, VM, Disk, Cloud Function, BigQuery, etc.
- Status: running, stopped, deallocated, terminated
- Specifications: vCPU, memory, OS, instance type, VM size
- Networking: Public/Private IP, Region, Availability Zone
- Operational Info: Launch time, lifecycle, billing type (On-Demand, Reserved, Spot)
- Tag Info: Name, Owner, Project, environment tags
✅ Examples of supported resources by cloud
- AWS: EC2, EBS, RDS, AMI, NAT Gateway, Elastic IP
- Azure: Virtual Machines, Disk, Load Balancer, Network Interface
- GCP: Compute Engine VM, Cloud Functions, BigQuery, Firewall
⚙️ Key Functional Benefits
- Status-based summary charts: Visualize the number of running, stopped, or deallocated instances
- Distribution insights: Identify resource concentration by type or region
- History view: Analyze changes in instance status and size over time with daily graphs
- Optimization integration: Surface recommendations like “Downsize” or “Modernize” to quickly spot cost-saving opportunities
❓ How frequently is resource data collected?
OpsNow automatically collects resource usage and metadata from each cloud provider using their official APIs, ensuring up-to-date visibility.
⏱ Standard Collection Interval
- Data is typically refreshed every 30 minutes to 1 hour for all connected accounts.
⏳ Exceptions for new regions or types
When new regions or resource types are introduced, data collection may be delayed based on provider-side availability:
| Cloud Provider |
Maximum Delay |
| AWS |
Up to 6 hours |
| Azure |
Up to 12 hours |
| GCP |
Up to 6 hours |
This ensures that organizations have near real-time access to resource data, which supports optimization efforts, idle instance detection, and operational accountability.
