AI impact analytics
Offering: GitLab.com, GitLab Self-Managed
-
Introduced in GitLab 16.11 with a flag named
ai_impact_analytics_dashboard
. Disabled by default. -
Generally available in GitLab 17.2. Feature flag
ai_impact_analytics_dashboard
removed. - Changed to require GitLab Duo add-on in GitLab 17.6.
The primary goal of AI impact analytics is to measure GitLab Duo’s impact on software development lifecycle (SDLC) performance. This dashboard provides visibility into key SDLC metrics in the context of AI adoption, helping you measure which metrics have improved as a result of AI investments.
Use AI impact analytics for:
- Correlation observations: Examine how trends in AI usage in a project or group influence other crucial productivity metrics. AI usage metrics are displayed for the last six months, including the current one.
- Snapshot of GitLab Duo usage: Track the use of seats and features in a project or group over the last 30 days.
To learn how you can optimize your license utilization, see GitLab Duo add-ons.
For a click-through demo, see the AI impact analytics product tour.
AI impact metrics
AI impact analytics displays key metrics and metric trends for a project or group.
Key metrics
-
Code Suggestions: Unique users: Percentage of users that engage with Code Suggestions every month. It is calculated as the number of monthly unique Code Suggestions users divided by total monthly unique contributors. Only unique code contributors, meaning users with
pushed
events, are included in the calculation. - Code Suggestions: Acceptance rate: Percentage of code suggestions provided by GitLab Duo that have been accepted by code contributors in the last 30 days.
- Duo Chat: Unique users: Percentage of users that engage with GitLab Duo Chat every month. It is calculated as the number of monthly unique GitLab Duo Chat users divided by the total GitLab Duo assigned users.
Metric trends
The Metric trends table displays metrics for the last six months, with monthly values, percentage changes in the past six months, and trend sparklines.
Lifecycle metrics
AI usage metrics
Code Suggestions usage: Monthly user engagement with AI Code Suggestions.
- The month-over-month comparison of the AI Usage unique users rate gives a more accurate indication of this metric, as it eliminates factors such as developer experience level and project type or complexity.
- The baseline for the AI Usage trend is the total number of code contributors, not just users with GitLab Duo seats. This baseline gives a more accurate representation of AI usage by team members. To learn more about AI impact analytics, see the blog post Developing GitLab Duo: AI impact analytics dashboard measures the ROI of AI.
- To analyze the performance of teams that use AI versus teams that don’t, you can create a custom Value Streams Dashboard Scheduled Report based on the AI impact view of projects and groups with and without GitLab Duo.
View AI impact analytics
Prerequisites:
- Code Suggestions must be enabled.
- ClickHouse for contribution analytics must be configured.
- On the left sidebar, select Search or go to and find your project or group.
- Select Analyze > Analytics Dashboards.
- Select AI impact analytics.
To retrieve AI impact metrics, you can also use the AiMetrics
, AiUserMetrics
, and AiUsageData
GraphQL APIs.
For an overview and sample queries, see issue 512931.