The Alert Is Real.
The Account Is Not Full.
The build account crossed ForgeFX’s static 2 TiB warning line. This is a retention and cost signal, not Azure’s physical capacity ceiling. TeamCity shows one recent local-agent disk-pressure event, but no build failure caused by disk exhaustion.
What Triggered It
Azure Monitor value: 2,203,026,754,557 bytes at 23:11 UTC
Recent build accumulation
Files modified in the last 30 days total 115.1 GiB. John Deere contributes 80.1 GiB, John Deere Pico 28.5 GiB, and John Deere Windows 5.2 GiB.
No automated retention
The account has no lifecycle management policy. Every listed blob remains in the Hot tier. Blob versioning is off; there are no snapshots or retained deleted blobs inflating the inventory.
Age Of Stored Builds
Current blob inventory, grouped by last-modified date
Where The Space Is
The top three containers hold 86.9% of all data
| Container | Size | Share | Blobs | Latest write |
|---|---|---|---|---|
| john-deere | 0.858 TiB | 42.8% | 934 | 23 Jul 2026 |
| holotrainer | 0.562 TiB | 28.0% | 973 | 21 Jan 2025 |
| halliburton | 0.322 TiB | 16.1% | 738 | 11 Dec 2025 |
| john-deere-pico | 0.136 TiB | 6.8% | 109 | 23 Jul 2026 |
| john-deere-windows | 0.080 TiB | 4.0% | 68 | 23 Jul 2026 |
TeamCity Disk-Space Cross-Check
208 finished builds reviewed across the last 30 days
No disk-caused build failure found
Forty-seven builds failed in the review window. Their logs and failure summaries showed tests, execution timeouts, Unity failures, and an upload-version conflict—not “disk full,” “no space left,” or ENOSPC failures.
One agent did run low
John Deere Unit Tests build 715 started on VM-05_BA-03 with 1.54 GiB free on its D: workspace. TeamCity cleaned it to 13.61 GiB before tests ran. The build later failed four tests, so local disk pressure was real but not causal.
| Evidence | Finding | Conclusion |
|---|---|---|
| Azure Blob Storage | 2.005 TiB against an internal 2 TiB alert | Retention / cost threshold |
| TeamCity agent workspace | 1.54 GiB free, auto-cleaned to 13.61 GiB | Temporary local disk pressure |
| Build failure cause | Four unit tests failed after cleanup completed | Not caused by disk space |
Recommended Response
No deletion or configuration change has been made
Approve retention by project
Ask each active project owner how many successful builds must remain immediately downloadable.
Tier before deleting
Move approved older builds to Cool or Archive first. The clearest review pool is the 1.277 TiB older than 180 days.
Automate the policy
Add lifecycle rules after owner sign-off, then replace the misleading “full” description with “crossed the 2 TiB operating threshold.”