RFC-015: Unified Observability Protocol (UOP) — 1. Purpose
AIGP Specification › RFC-015: Unified Observability Protocol (UOP) › 1. Purpose
Section index · 2. Signal Types →
RFC-015: Unified Observability Protocol (UOP)
PRIVATE AND PROPRIETARY — NOT A PUBLIC RFC. Owned by Kanjani AI Research & Causum. See NOTICE.md.
1. Purpose
The Unified Observability Protocol (UOP) defines a standardized observability layer across all four amigos (identity-service, analytics-service, governance-server, runbook-service). UOP centralizes telemetry collection, dashboarding, alerting, and request tracing within governance-server the observability hub.
UOP SHALL ensure:
- all protocol traffic (AIGP, ACP, ALP) is observable from a single pane of glass
- system health is continuously monitored via heartbeats and signal volume
- budget consumption, error rates, and latency are tracked per-app, per-model, per-use-case
- a single user request can be traced across all four amigos via request ID propagation
- alerting is built into governance-server with no external dependencies (no Prometheus, no Grafana)
- all observability data is stored in DynamoDB using the existing governance-server single-table design