Operational Health
Operational Health reports on the platform's own health — not the cloud bill. It shows fleet-wide sync freshness, recent failures, and data-quality probes across every company, so you can trust that the cost and asset data elsewhere in Beak FinOps is current.
Headline Tiles
Companies are summarized by sync status:
- Healthy — Recent, successful syncs
- Stale — Data older than expected
- Failing — The most recent sync failed
- Not configured — No cloud credentials configured yet
Companies Table
| Column | Description |
|---|---|
| Company | The company name |
| Status | Healthy, Stale, Failing, or Not configured |
| Azure | Azure sync result |
| AWS | AWS sync result |
| Last sync | Time since the last successful sync |
Click a row to open that company's sync history. A single row can show both Azure and AWS results — Operational Health is cloud-agnostic.
Data Quality Signals
Below the table, data-quality signals flag issues such as companies with no cloud credentials configured, with a pointer to fix them under Companies → Credentials.
Best Practices
- Check daily — A quick scan confirms the whole fleet's data is fresh
- Fix Failing first — A failing sync means stale data for that company until resolved
- Resolve Not configured — Add credentials so a company starts collecting data