Learn
diagnosis
2 registry resources · 2 tutorials · roadmap: Lakehouse, Cloud
What this topic covers
DE//AGENT currently lists 2 resources under diagnosis: 2 tutorials. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.
What you can learn here
Documented learning objectives across these resources:
- Recognize the small-files signature from file sizes and planning time — via Diagnose a small-files explosion
- Query metadata tables to quantify fragmentation — via Diagnose a small-files explosion
- Fix the layout, not just the symptoms — via Diagnose a small-files explosion
- Attribute a cost spike to a stage with run-over-run byte diffs — via Incident — the job that quadrupled in cost overnight
- Tell apart fan-out, lost filters, and small-file regressions — via Incident — the job that quadrupled in cost overnight
- Cap the damage with resource monitors and unit-metric alarms — via Incident — the job that quadrupled in cost overnight
Where this fits in the learning roadmap
These resources map to stages: Lakehouse (1), Cloud (1). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.
Compare the registry's options
Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| Diagnose a small-files explosion | Tutorial | intermediate | community | 34.15 |
| Incident — the job that quadrupled in cost overnight | Tutorial | intermediate | community | 34.15 |
How scores are computed: source quality score.
Where to start
Highest composite score first:
- Diagnose a small-files explosion score 34.15 — intermediate
- Incident — the job that quadrupled in cost overnight score 34.15 — intermediate
Scores rank provenance, completeness and trust — read how verification works before adopting anything.
Production use cases
- Diagnose a small-files explosion — Follow the small-files runbook from symptom to prevention: confirm the tens-of-thousands-of-tiny-files signature, query the metadata tables for the average file size, compact to a … details
- Incident — the job that quadrupled in cost overnight — An invoice alert or a cost-per-run dashboard spike lands: one job's compute cost quadrupled with no functional change. Work the runbook — diff shuffle write and input bytes run-ove… details
Further study
Adjacent topics: tutorial (2 shared).
Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.
Full resource list
| Resource | Type | Score |
|---|---|---|
| Diagnose a small-files explosion | Tutorial | 34.15 |
| Incident — the job that quadrupled in cost overnight | Tutorial | 34.15 |