Design: Monitoring & Logging Integration
## Objective Design and document the monitoring and logging integration approach for OAK in GA. ## Design Document Reference Addresses the open question in the [OAK Design Document - 6. Monitoring & Logging Integration](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/omnibus_adjacent_kubernetes/#6-monitoring--logging-integration) ## Scope Design observability integration between Omnibus and Kubernetes components: - **Omnibus Prometheus integration**: Evaluate options for exposing Omnibus metrics - **Kubernetes metrics scraping**: Design metrics collection from Kubernetes components - **Log aggregation**: Design log aggregation approach for both Omnibus and Kubernetes - **Observability patterns**: Document recommended patterns for users ## Deliverables - **ADR Document**: Added to the OAK Beta Design Document with: - Evaluation of Omnibus Prometheus integration options - Design of metrics scraping from Kubernetes components - Design of log aggregation approach - Final decision and rationale - Impact on operational visibility and troubleshooting ## Follow-up Work If implementation is required, a follow-up issue will be created in the [OAK - GA Rollout Implementation](https://gitlab.com/groups/gitlab-com/gl-infra/software-delivery/-/work_items/87) epic. ## Related Documentation - [OAK Design Document](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/omnibus_adjacent_kubernetes/) - [Phase 4 Epic #85](https://gitlab.com/groups/gitlab-com/gl-infra/software-delivery/-/work_items/85)
issue