Monitoring & Savings
Track runtime state, action history, and cost savings across linked AWS connections in your Runless tenant.
Overview
Monitoring data is available directly in dashboard workflows:
- Header savings for tenant-level realized savings
- Notifications for recent service state changes
- Service history for per-service shutdown/startup cycles
- Cluster cost panels for projected versus realized savings context
Tenant Savings (Header)
The top header displays total realized savings for your tenant based on recorded runtime downtime across linked accounts.
Notifications
The notification bell shows recent service status events with service identity, status, and timestamp.
These updates are delivered as real-time control-plane events to active dashboard sessions.
Service Runtime History
To inspect one service:
- Select AWS account and cluster
- Open service configuration panel
- Open History tab
| Column | Description |
|---|---|
| Shutdown | Stop timestamp and trigger type (scheduled/manual) |
| Startup | Start timestamp and trigger type |
| Saved Duration | Downtime length for the cycle |
| Amount Saved | Estimated cost saved during that downtime |
Savings Calculation
Runless estimates per-cycle savings using downtime, task cost profile, and restored task count:
Amount Saved = Hours Stopped x Cost per Task per Hour x Desired Task Count
Projected monthly savings in rule editors use the same pricing model with schedule-based runtime assumptions.
Teams commonly save 40-60% in non-production ECS environments when schedules are aligned to working hours and weekend inactivity.
Cluster Cost Metrics
For the selected cluster, the dashboard summarizes:
- Current hourly cost
- Gross monthly cost (without savings)
- Estimated monthly savings from active schedules
- Net monthly cost
- Realized savings to date
Operational Troubleshooting
If monitoring values look incorrect:
- Refresh inventory and service history for the connection
- Confirm the connection remains verified and commercially active
- Review recent runtime action outcomes in history and notifications
- Check backend logs for persistent API or runtime failures
External Logs
Runless does not include a full in-app raw log viewer. For deep diagnostics, inspect AWS logs available to your operations environment, including control-plane and runtime execution logs.