How we plan to build more observability tools on GitLab monitoring

This post outlines GitLab's strategy and roadmap for expanding its observability tools. It details the vision for monitoring within the DevOps lifecycle, emphasizing ease of instrumentation, proactive issue resolution, and seamless insight gathering. Key areas of development include enhancing metrics collection (building on Prometheus integration), simplifying Kubernetes cluster monitoring (including memory/CPU usage and cost optimization), and developing a new incident management system based on GitLab issues. The post also highlights the 'dogfooding' approach, where internal teams use these developing tools, and the strategy to expose these capabilities to administrators of self-managed GitLab instances. The core challenge identified is the evolving industry consensus on what constitutes a robust observability suite in a cloud-native world.
More from the Log Management and Observability trail
- Green DevOps: Why carbon measurement belongs in your CI/CD pipeline
- Automate detection testing with GitLab CI/CD and Duo
- How to build CI/CD observability at scale
- Track vulnerability remediation with the updated GitLab Security Dashboard
- More granular product usage insights for GitLab Self-Managed and Dedicated