Skip to content

Generated SaaS — 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.product.tenants GeneratedSaasFoundations updown productId, state
connectsoft.factory.product.subscriptions GeneratedSaasFoundations updown productId, edition
connectsoft.factory.product.health GeneratedProductHost gauge productId, service
connectsoft.factory.product.requests GeneratedProductHost counter productId, context, outcome

What a product emits

Every generated product carries the observability libraries from its Observability Blueprint: OpenTelemetry traces, metrics and logs with connectsoft.factory.product_id, release_id and the opaque customer_tenant_id, GenAI attributes where the product embeds agents, and health endpoints per service. Raw prompt and response logging is off by default (D31).

Signal Why the Factory reads it
connectsoft.factory.product.health per service fleet probes mark instances Degraded; incidents open by rule
connectsoft.factory.product.requests by context and outcome product objectives (availability, error rate) per edition floor
connectsoft.factory.product.tenants, subscriptions instance inventory and version skew per customer tenant
ProductUsageMetered events managed-product cost attribution (later)

Where it goes

The product exports to the installation's OpenTelemetry backend (the owner's or ConnectSoft's for managed products); SloService measures product objectives with instances as subjects; FleetInventoryService probes health through GW-07; FleetIncidentService opens incidents from alerts.