Comprehensive Build and Job Statistics Dashboard for GitLab CI/CD
Proposal
We propose adding a dashboard feature in GitLab that provides a comprehensive view of build and job statistics, similar to what is available in Jenkins. This dashboard would display aggregated data from multiple runners, projects, and groups, enabling users to quickly monitor:
- Total number of builds and their statuses (e.g., Failed, Success, Running, Aborted) across multiple projects/groups.
- Job health metrics, such as the percentage of failed/successful builds over time.
- Real-time status of runners, including ongoing jobs and runner availability.
Technical Details:
- Leverage the existing APIs for Runners (
/runners) and Pipelines (/pipelines) to gather statistics and metrics across various namespaces. - Integrate the data into an accessible, centralized dashboard that could be part of GitLab's existing Runner fleet dashboard (available in the Ultimate tier) or a new feature for broader tiers (e.g., Premium and Free).
- Ensure scalability for users with multiple runners and groups by providing filters for different namespaces and projects.
How It Would Help:
This feature would improve visibility across CI/CD pipelines, especially for teams managing multiple projects or large-scale setups with distributed runners. By centralizing job health and build statuses into one dashboard, teams can quickly identify problematic jobs, monitor runner performance, and take timely action.
Without this feature, teams currently need to rely on manual API requests or third-party solutions, leading to increased operational overhead and delays in identifying issues. An integrated solution within GitLab would streamline this process and reduce the need for external tools.
What does success look like, and how can we measure that?
Success for this feature would be measured by:
- Reduced time for teams to gather build and job status information across projects.
- Improved monitoring of runner and job health, allowing teams to proactively manage runner capacity and job failures.
- Increased user satisfaction with GitLab's CI/CD pipeline monitoring, particularly for large enterprises or teams with complex setups.
Feel free to paste this into your feature proposal form.