id:
cap-otel-portal · owner: finaya-platformDescrição
OTel SDK setup + 4 counters + 4 gauges em portal-finaya runtime
Enterprise Architecture derivado
RACI
Accountable:
SRE_LEAD declaradoResponsible: PLATFORM_ENGINEERMaturidade (1–5)
people3process3technology4information3
Dispara (triggers)
—Data access (Entity:CRUD)
OtelMetric:CImportância (proxy)
0
consumidores×2 + fan-out
Governança do catálogo 6 capabilities
✓ todas as capabilities com dono têm accountable declarado
✓ nenhuma entidade com dono ambíguo (2+ criadores)
Sustentação operacional
FTE/ano
0.05
Runtime USD/mês
0
Custo aprox/ano (USD)
7500
FTE × 150k + runtime × 12
Demand evidence
- dashboard-07: consume metrics
History (transições)
2/2filtrar stages:
| Stage | Timestamp | Rationale |
|---|---|---|
| experimental | 2026-05-08T00:00:00Z | Sprint 40 setup |
| adopted | 2026-05-08T00:00:00Z | wired ingest+webhook |
Audit log (CockpitFeed)
0 eventos carregadosSprint 97 · cursor-paginated · canonical em CockpitFeedNenhum evento desta capability no buffer atual. Eventos antigos podem ter expirado pela retention policy (capability.promoted: 30d).
✓ fim do buffer · eventos mais antigos podem ter expirado
Bench scenarios
0 runs recentesSprint 112 · scenario_id = cap-otel-portal · ring buffer (500)↓ CSV 30dver todos no bench →Sem runs do scenario cap-otel-portal no buffer atual. Rodar via
POST /api/bench/event ou CI nightly.ADRs relacionadas
1 ADRsSprint 122 · expand inline para PDFSprints 32-36: Redis multi-replica + Circuit breaker + Listener pool + Tailwind eval + Dashboard 07
Redis token bucket + Circuit breaker + Listener pool + Tailwind WAIT + SignOz dashboard alert-adapter
related: ADR-045, ADR-044, ADR-019, ADR-040
Edição
Edita description, owner, sustentação, promotion_adr e demand_evidence. Para promover stage, use o flow board.