Observability

Observability

Catalogue verified operational signals and diagnostic workflows.

Status: Partial implementation reference — Code-confirmed; operational validation pending

Last reviewed: 2026-10-19

Scope

Logs, metrics, traces, alerts, access requirements and investigation guidance where applicable. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.

Current implementation baseline

Worker configuration enables platform observability. Source logs include event-pump cursor/batch progress, Corpus materialization results/failures and MCP authentication/event delivery diagnostics. These statements identify logging code, not verified dashboards, retention, alerts or redaction policy.

Inspect Events logs, Corpus scheduled handler, MCP router and Event Hub. Corpus health returns basic service metadata and is not a dependency-wide health check.

Source does not establish numeric service targets, production hit rates or an escalation rota. The existing performance/caching audit records measurement limitations. Record environment, source revision and safe correlation data when investigating; avoid exposing credentials or private recovery payloads.