Architecture: How to build observability dashboard for the platform?
Documentation for Sessions
🏗️ Architecture: How to build observability dashboard for the platform?
Date: 2026-02-26
Time: 16:18:43 UTC
Session: gspace1-144.4
Agent: angular
Confidence: 90%
Status: ✅ Documented
📋 Decision Context
Question:
How to build observability dashboard for the platform?
Task: Add observability dashboard (Gap 11)
🎯 Decision Made
Chosen:
Backend ObservatoryService aggregates health from all 4 backends with 30s cache, LlmCostTrackerService tracks 24h rolling window, ObservatoryController serves JSON dashboard + Prometheus metrics. Frontend ObservatoryDashboardComponent polls every 30s.
Options Considered:
- No alternatives documented
💭 Reasoning
In-memory approach avoids new MongoDB schema overhead. 30s health cache prevents hammering backends. Prometheus text format enables future Grafana/AlertManager integration. Frontend tab system extends existing observatory page without breaking Chrome extension embedding.
📁 Files Involved
APIs/backend-ai-api/src/app/infrastructure/services/observatory.service.tsAPIs/backend-ai-api/src/app/infrastructure/services/llm-cost-tracker.service.tsAPIs/backend-ai-api/src/app/infrastructure/controllers/observatory.controller.tslibs/libs-ai/gograb-ai-lib/src/lib/components/observatory-dashboard/observatory-dashboard.component.tslibs/libs-ai/gograb-ai-lib/src/lib/services/observatory-data.service.tsapps/gograb-ai/src/app/pages/observatory/observatory-page.component.ts
🔗 Related
- Decision ID:
dev_1772122723633_reubyc9 - Session: 144
- Workspace: gspace1
Auto-generated by MCP Smart Consolidation