Export the live architecture map as Backstage catalog entities, so an
existing Backstage instance gets a catalog that updates itself from logs.
Scope
GET /api/v1/catalog/export?format=backstage — a multi-document
catalog-info.yaml: one kind: Component per service, dependsOn
derived from the observed edges, metadata from the catalog fields
(#owner/description/links, see the catalog-fields issue);- stable URL suitable for Backstage's URL reader / location mechanism —
point Backstage at LogDoc once, dependencies stay current;
- Port sync (via their API) as a follow-up if there is demand.
Why
"The catalog is stale" is the standing complaint about hand-maintained
service catalogs. LogDoc already derives the dependency graph from logs
alone; exporting it in Backstage's native format turns that into an
auto-population layer for catalogs teams already run.
Export the live architecture map as Backstage catalog entities, so an
existing Backstage instance gets a catalog that updates itself from logs.
Scope
GET /api/v1/catalog/export?format=backstage— a multi-documentcatalog-info.yaml: onekind: Componentper service,dependsOnderived from the observed edges, metadata from the catalog fields
(#owner/description/links, see the catalog-fields issue);
point Backstage at LogDoc once, dependencies stay current;
Why
"The catalog is stale" is the standing complaint about hand-maintained
service catalogs. LogDoc already derives the dependency graph from logs
alone; exporting it in Backstage's native format turns that into an
auto-population layer for catalogs teams already run.