GitLab Duo and SDLC trends

This feature is in beta for GitLab Self-Managed. For more information, see epic 51.

GitLab Duo and SDLC trends measure the impact of GitLab Duo on software development lifecycle (SDLC) performance. This dashboard provides visibility into key SDLC metrics in the context of AI adoption for projects or groups. You can use the dashboard to measure which metrics have improved from your AI investments.

Use GitLab Duo and SDLC trends to:

• Track SDLC trends in relation to your GitLab Duo journey: Examine how trends in GitLab Duo usage in a project or group influence other crucial productivity metrics such as mean time to merge and CI/CD statistics. GitLab Duo usage metrics are displayed for the last six months, including the current one.
• Monitor GitLab Duo feature adoption: 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.

To learn more about GitLab Duo and SDLC trends, see the blog post Developing GitLab Duo: AI impact analytics dashboard measures the ROI of AI.

For a click-through demo, see the GitLab Duo and SDLC trends product tour.

For an overview, see GitLab Duo AI Impact Dashboard.

Key metrics

• Assigned Duo seat engagement: Percentage of users that are assigned a GitLab Duo seat and used at least one AI feature in the last 30 days. It is calculated as the number of users with GitLab Duo seats that use AI features divided by the total number of assigned GitLab Duo seats.
• Code Suggestions usage: Percentage of users with assigned GitLab Duo seats that used Code Suggestions in the last 30 days. It is calculated as the number of unique users with GitLab Duo seats that interact with Code Suggestions divided by the total number of unique code contributors (users with pushed events) with GitLab Duo seats. For calculating Code Suggestions metrics, GitLab collects data only from code editor extensions.
• Code Suggestions acceptance rate: Percentage of code suggestions provided by GitLab Duo that have been accepted by code contributors in the last 30 days. It is calculated as the number of accepted code suggestions divided by the total number of generated code suggestions.
• Duo Chat usage: 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.

GitLab Duo usage metrics

• Code Suggestions usage: Monthly user engagement with AI Code Suggestions.

  On GitLab.com, data updates every fives minutes. GitLab counts Code Suggestions usage only if the user has pushed code to the project in the current month.

  The month-over-month comparison of the AI Usage unique users rate gives a more accurate indication Code Suggestion usage, because 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 only users with GitLab Duo seats. This baseline gives a more accurate representation of AI usage by team members.

  Usage rate for Code Suggestions is calculated with data starting from GitLab 16.11.

• Duo RCA usage: Monthly user engagement with GitLab Duo Root Cause Analysis. Tracks the percentage of GitLab Duo users who use GitLab Duo Chat to troubleshoot a failed CI/CD job from a merge request.

  Usage rate for GitLab Duo RCA is calculated with data starting from GitLab 18.0.

• Duo features usage: Number of contributors who used any GitLab Duo feature.

• Duo Code Review requests: Number of GitLab Duo Code Review requests made on merge requests. This includes requests initiated by both merge request authors and non-authors.

• Duo Code Review comments: Number of comments posted by GitLab Duo Code Review on merge request diffs.

  Usage data for Duo Code Review requests and comments is calculated with data starting from GitLab 18.3.

Development metrics

• Lead time
• Median time to merge
• Deployment frequency
• Merge request throughput
• Critical vulnerabilities over time
• Contributor count

Pipeline metrics

The Pipeline metrics table displays metrics for the pipelines run in the selected project.

• Total pipeline runs: Number of pipeline runs in the project.
• Median duration: Median duration (in minutes) of a pipeline run.
• Success rate: Percentage of pipeline runs that completed successfully.
• Failure rate: Percentage of pipeline runs that completed with failures.

Code Suggestions acceptance rate by language

The Code Suggestions acceptance rate by language chart displays the acceptance rate of Code Suggestions broken down by programming language for the last 30 days.

The acceptance rate for each language is calculated as the number of accepted code suggestions divided by the total number of code suggestions shown.

Code generation volume trends

The Code generation volume trends chart displays the volume of code generated through Code Suggestions over the last 180 days, aggregated by month. The chart shows:

• Lines of code accepted: Lines of code from Code Suggestions that were accepted.
• Lines of code shown: Lines of code displayed in Code Suggestions.

GitLab Duo Code Review requests by role

The GitLab Duo Code Review requests by role chart displays the number of GitLab Duo Code Review requests over the last 180 days, aggregated by month. The chart shows:

• Review requests by authors: Number of GitLab Duo Code Review requests made by the merge request author. This includes code reviews requested automatically through the project setting and manually in the merge request by the author.
• Review requests by non-authors: Number of GitLab Duo Code Review requests made by users other than the merge request author. For example, reviewers who ask GitLab Duo to review the merge request changes.

Higher author adoption indicates teams embracing automated review workflows.

View GitLab Duo and SDLC trends

Prerequisites:

• Code Suggestions must be enabled.
• For GitLab Self-Managed, ClickHouse for contribution analytics must be configured.

1. On the left sidebar, select Search or go to and find your project or group. If you’ve turned on the new navigation, this field is on the top bar.
2. Select Analyze > Analytics Dashboards.
3. Select GitLab Duo and SDLC trends.

To retrieve GitLab Duo and SDLC metrics, you can also use the AiMetrics, AiUserMetrics, and AiUsageData GraphQL APIs.