Last updated: September 2025
Overview
GitKraken Insights provides a unified analytics platform integrated directly into developer workflows. It transforms raw Git activity and development metrics into actionable insights for teams and leaders. By combining code activity data, PR metrics, issue tracker integration, and CI/CD performance, dashboards deliver context-rich metrics that help optimize the entire development lifecycle.
Key benefits
- Workflow-integrated insights: Access metrics derived directly from developer tools, with visibility into the impact of AI on development teams—without disrupting workflows.
- Context-rich metrics: Go beyond vanity metrics by connecting code changes to business objectives through issue linking, PR quality analysis, benchmark goals/alerts, and work investment categorization.
- Improvement pathways: Get personalized recommendations that identify inefficiencies and provide guided action plans to improve productivity.
Adding Metrics
Before you can add metrics, complete these setup steps:
- Request access to GitKraken Insights.
- Connect GitKraken Insights to your GitHub account.
- Wait for your repositories to finish importing. For detailed instructions, see the Getting Started guide.
Once setup is complete, open the Insights > Dashboard tab from gitkraken.dev.
Add a metric
- In the Dashboard view, click the Add Metric button in the top-right corner.
- Browse the list of available widgets, grouped by category (for example, DORA and Pull Requests).
- Click Add next to the metric you want to display on your dashboard.
Available metrics
DORA metrics
- Deploy Frequency
- Change lead time
- Mean time to repair/recover
- Defect rate (% of deploy with severe defect)
Pull Request metrics
- First response time (“Pickup time”)
- Cycle time (“first commit” to “merge”)
- Lead time (“first commit” to “deployed”)
- Number of reviews per day/week/month
Deploy Frequency
This metric shows how often new code is released or deployed to production, measured as the number of deployments per day, week, or other selected timeframe.
In addition to the main chart, the following submetrics are displayed when you click the Details button:
- Deployments per day
- Lead time for changes
- Average hours to repair (MTTR)
- Change failure rate
Change Lead Time
This metric shows how long each pull request within a selected timeframe took to go from the first commit until it was deployed. Values are expressed in days and are calculated over a rolling 7-day period.
Mean Time to Repair/Recover (MTTR)
This metric shows how long each pull request within a selected timeframe took to go from the first commit until it was deployed. Values are expressed in days and calculated over a rolling 7-day period. Lower MTTR indicates that teams can respond quickly to incidents and minimize downtime.
Defect Rate
This metric shows the number of defects detected over time. Values are expressed as defects over a rolling 7-day window. A lower defect rate indicates a more stable and reliable deployment process.
First Response Time (“Pickup Time”)
This metric shows how long each pull request within a selected timeframe took to have a first response (comment or review). Values are expressed in hours and averaged over a 7-day period. Shorter pickup times indicate faster reviewer engagement and healthier collaboration.
Cycle Time (“first commit” to “merge”)
This metric shows how long each pull request within a selected timeframe took to merge from the time the first commit was made. Values are expressed in days and averaged over a 7-day period. Cycle time provides insight into overall delivery speed, highlighting how quickly work moves from coding to production.
The Details view offers deeper analysis.
- Pull requests are grouped into four categories by duration:
- Elite: Less than 1 day
- Fast: 1–7 days
- Average: 7–29 days
- Slower: Over 30 days
- Each node in the scatter plot is interactive, showing PR details such as time since merge, PR name, author, and a link to open directly in GitHub.
- A sortable table lists all PRs below the chart. You can sort by Days, Pull Request name, Author, Date Opened, or Date Merged.
Lead Time
This metric shows how long each pull request within a selected timeframe remained open, measured from when the PR was created until it was merged. Values are expressed in days and averaged over a 7-day period.
Number of Reviews per Day/Week/Month
This metric shows the total number of reviews (all types) completed over a given period of time. Values are expressed in reviews and averaged over a 7-day window. Tracking review activity helps teams understand collaboration patterns and reviewer workload across different timeframes (daily, weekly, or monthly).
Layout
Widgets on the dashboard can be customized to fit your needs.
- Resize widgets: Each widget is available in two sizes—small or large. Drag and drop the lower-right corner of a widget to adjust its size.
- Rearrange widgets: Drag and drop from the upper-left corner of a widget to move it into a new position on the dashboard.
- One per dashboard: Only one copy of each metric can be placed on a dashboard.
Filters
The dashboard may be filtered by Workspace, Repositories, Timeframe, and Team.
-
Workspace: Workspaces are preset groups of repositories. They also enable other key features across gitkraken.dev, GitKraken Desktop, GitLens, and the GitKraken CLI such as Launchpad and multi-repo actions. On the dashboard, you can filter to only display data for the repositories in your chosen Workspace. To create your first workspace, go to gitkraken.dev/workspaces.
-
Repositories: Refers to the list of repos imported into GitKraken Insights. Check or uncheck repositories to fine-tune the data. Use the search feature to quickly locate repos by name.
-
Timeframe: Sets the timebox for the dashboard. Options include This Week, Last Week, Last 7 days, Last 14 days, Last 28 days, Last 30 days, Last 90 days, Last 12 months, or a custom date range.
-
Team: Filters the data by a group of users. Teams can be configured at gitkraken.dev/teams.
