Skip to main content

Operating Model

Observability is not owned by one team. It is a shared responsibility model with clear boundaries, aligned to G.A.I.N AIOM plane thinking.

RACI summary

ActivityProductEngineeringPlatformSREArchitecture
Define business KPIs and journeysA/RCICC
Map KPI → service entryCRICA
Service instrumentationIRCCA
Infra / K8s / DB telemetryICRCA
Correlation standardsCCRCA
Alert registry and pagingCCCR/AC
Dashboards (canonical)CCRRA
Maturity roadmapCCCCA/R
Audit / replay consumersCCRCA

R = responsible · A = accountable · C = consulted · I = informed

Team charters (one paragraph each)

Product

Owns what success looks like for customer and regulatory journeys. Defines outcome KPIs, business SLOs, and journey steps. Does not own Prometheus or log pipelines.

Engineering

Owns service instrumentation: golden signals, traces, dependency accuracy, and feature-level SLIs. Ships code that emits structured logs and propagates correlation IDs.

Platform

Owns observability infrastructure: collectors, stores, retention tiers, enrichment, cost attribution, and self-service onboarding templates.

SRE / reliability

Owns alerting, incident response, and error budgets. Maintains alert registry, runbooks, and drill programs. Escalates when business SLOs burn.

Architecture

Owns standards and the correlation model: governance rules, maturity targets, tool boundaries, and cross-domain graph design. Resolves layer-mixing debates (strategy vs system vs software).

Cadence

MeetingFrequencyOutput
SLO reviewMonthlyError budget decisions
Journey / KPI reviewQuarterlyUpdated business maps
Maturity assessmentSemi-annualRoadmap refresh
Graph drillQuarterlyE2E trace evidence

AI-specific overlay

When agents or RAG are in scope, add:

RoleAdded responsibility
AI platformRequest-path spans, eval sampling hooks
Security / complianceAudit tier access, redaction policy
Model risk (regulated)Quality metrics as control evidence

Bridge: G.A.I.N Observability · Eval Engineering playbooks.

Release gate

  • RACI published for observability workstreams
  • Named owners for tier-1 journeys and services
  • Monthly SLO review on calendar
  • Architecture sign-off on correlation standard