17 · Service catalog, live health
Estate catalog and status
A catalog no one keeps by hand: built from what is published.
A developer portal whose catalog is generated from the manifests that publish the services, with docs assembled from each repo behind a redaction gate, and a collector that reads container health and disk from outside the portal.
- 01Generated, not maintained — the catalog is built from the publishing manifest on every run.
- 02What runs where — every component depends on its host; hosts are resources under one infrastructure system.
- 03Drift warnings — an unmapped service, or a mapping to a service that is gone, is reported on every run.
- 04Honest status — the collector reads each host from outside; a host it cannot reach shows unknown, never up.
- 05Disk alerts that outlive the portal — per-host thresholds, emailed on breach and on recovery.
Internal
- 112 catalog components
- 28 systems
- 30 collector tests
SurfacesWebAPI
- Backstage
- TechDocs
- PostgreSQL
- Python
- Node 22
- Docker Compose