Skip to content

Factory Studio — 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.studio.screen_latency StudioBff histogram screenId
connectsoft.factory.studio.commands_forwarded StudioBff counter commandId, outcome
connectsoft.factory.studio.sessions_active StudioBff updown tenant, locale
connectsoft.factory.studio.source_degraded StudioBff updown source
connectsoft.factory.studio.notifications StudioNotificationService counter tenant, kind, channel
connectsoft.factory.studio.notification_latency StudioNotificationService histogram kind
connectsoft.factory.studio.realtime_connections StudioRealtimeGateway updown tenant
connectsoft.factory.studio.realtime_push_latency StudioRealtimeGateway histogram kind
connectsoft.factory.studio.realtime_refreshes StudioRealtimeGateway counter kind

The platform's signals

Signal Why it matters
connectsoft.factory.studio.screen_latency per screen the interactive objective (2 s p95, D30) measured where the person waits
connectsoft.factory.studio.commands_forwarded by outcome how often users hit 403, 409 and 412, which is a design signal as much as an operations one
connectsoft.factory.studio.source_degraded which platforms the Studio could not reach, and for how long
connectsoft.factory.studio.sessions_active by locale adoption per locale; RTL usage
connectsoft.factory.studio.notification_latency, realtime_push_latency, realtime_refreshes whether the live experience is live

Client telemetry

The web Studio, CLI and VS Code extension emit OpenTelemetry spans for navigation and commands with the same connectsoft.factory.* attributes and the session id, joined to the BFF's spans by trace context; no content, prompts or artifact bodies are ever in client telemetry. Web vitals per screen feed the interactive objective.