Template & Library — observability¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
| Metric | Service | Instrument | Dimensions |
|---|---|---|---|
connectsoft.factory.blueprints.versions |
BlueprintService | counter | tenant, kind, state |
connectsoft.factory.blueprints.validation_failures |
BlueprintService | counter | kind, ruleId |
connectsoft.factory.templates.host.inbox_lag |
TemplateCatalogHost | gauge | module |
connectsoft.factory.recipes |
GenerationRecipeService | counter | tenant, state |
connectsoft.factory.recipes.generated_modules |
GenerationRecipeService | counter | tenant, kind, templateId |
connectsoft.factory.recipes.validation_failures |
GenerationRecipeService | counter | reason |
connectsoft.factory.templates.versions |
TemplateRegistryService | updown | kind, layer, state |
connectsoft.factory.templates.compatibility_unknown |
TemplateRegistryService | updown | subjectKind |
The platform's signals¶
| Signal | Why it matters |
|---|---|
connectsoft.factory.blueprints.versions, validation_failures by rule |
which rules trip most is a design signal for the blueprint schemas and the agents that author them |
connectsoft.factory.templates.versions, compatibility_unknown |
the health of the building material and the evidence gap in the matrix |
connectsoft.factory.recipes by state, generated_modules by template, validation_failures by reason |
throughput of design-to-generation and which templates carry the product |
Where they go¶
Generation runs are ordinary runs in the operations projections; recipe and blueprint events reach the run timeline; template adoption feeds the later template analytics (BC-22). Spans carry connectsoft.factory.blueprint_id, recipe_id, template_id, template_version.