Skip to content

Data & Event Platform — 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.data_event.host.registry_lookups DataEventFoundations counter kind
connectsoft.factory.data_event.topics EnvelopeRegistryService updown state
connectsoft.factory.data_event.envelope_validation_failures EnvelopeRegistryService counter producer, topic
connectsoft.factory.data_event.store_bindings StoreProfileService updown storeClass, region, state
connectsoft.factory.data_event.binding_drift StoreProfileService counter kind
connectsoft.factory.data_event.orders RetentionResidencyService updown tenant, kind, state
connectsoft.factory.data_event.order_completion_days RetentionResidencyService histogram kind
connectsoft.factory.data_event.residency_violations RetentionResidencyService counter tenant, kind

The platform's signals

Signal Why it matters
connectsoft.factory.data_event.topics by state, envelope_validation_failures a producer emitting an unregistered or invalid event is a release defect, visible immediately
connectsoft.factory.data_event.store_bindings, binding_drift where data lives, and whether provisioning and the registry agree
connectsoft.factory.data_event.orders by state, order_completion_days the 30-day deletion commitment, measured
connectsoft.factory.data_event.residency_violations every refused binding, deployment or connector choice

Signals every host reports under the messaging profile

The messaging adapters emit, per host: outbox depth and oldest-row age, dispatch latency, inbox deduplication hits, dead-lettered envelopes by topic, and delivery attempts. The Observability platform turns outbox age into a platform objective (EvidenceLag), because an undeliverable outbox makes a service unreachable in effect even when its health probe is green.