## **Summary** This issue proposes the development of a comprehensive organization-level dashboard for artifact management in GitLab. This dashboard will provide administrators and platform engineers with a centralized view of artifact usage, health metrics, and package-specific policies across all groups and projects. ## **Background and Opportunity** Enterprise organizations require a holistic view of their artifact ecosystem to make informed decisions about governance and package management. The organization-level dashboard will address this need by aggregating data across all groups and projects, providing a "single pane of glass" for artifact management oversight. ## **User Personas and Pain Points** ### **GitLab Administrators** * Lack of consolidated view of artifact usage across the organization * Need better visibility into registry performance and health * Require insights into upstream repository status * Want to standardize artifact-related policies across groups ### **Platform Engineers** * Need to understand artifact interdependencies across projects * Lack visibility into upstream repository performance organization-wide * Want to standardize cleanup policies across multiple groups * Need to identify high-impact optimization opportunities ## **Dashboard Features and Capabilities** ### **1. Executive Summary View** * **Organization-wide package metrics** with trend analysis * **Registry health status** overview with critical alerts highlighted * **Usage patterns** showing activity across the organization * **Package distribution** by type, group, and project ### **2. Registry Health and Performance** * **Upstream repository health** metrics across all registry types * **Performance trends** for artifact pulls and pushes * **Availability metrics** with historical uptime * **Bandwidth usage** by region and group * **Pull-through cache effectiveness** metrics ### **3. Usage Analytics** * **Package consumption metrics** across groups and projects * **Dependency relationships** visualization * **User activity tracking** with access patterns * **Pipeline integration metrics** * **Most active packages** by download count * **Package activity trends** over time ### **4. Package Lifecycle Management** * **Package aging visualization** across the organization * **Version distribution** showing package version spread * **Release cadence** metrics for regularly updated packages * **Package abandonment detection** for unmaintained artifacts ### **5. Artifact Policy Management** * **Cleanup policy visualization** across groups and projects * **Retention rule effectiveness** metrics * **Policy standardization opportunities** highlighting inconsistencies * **Package protection rules** overview * **Virtual registry configuration** status and health ## **Next Steps** * Conduct user research with enterprise customers to validate requirements * Develop detailed wireframes and prototypes for key dashboard views * Create technical design for data aggregation and processing * Establish metrics framework for measuring dashboard effectiveness <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->